[Xcb] Bug#912189: libpthread: man pthread_mutex_init doesn't find a man page

[Joshua]

Package: libpthread-stubs0-dev
Version: 0.3-4
Severity: normal
File: libpthread
Tags: newcomer

It's possible I don't quite have the right package.

man pthread_init does not find a man page but should. I'm not certain but I think one can be thrown
together pretty quickly from the one on the open group.


-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

[Josh Triplett]

Post by Joshua
Package: libpthread-stubs0-dev
Version: 0.3-4
Severity: normal
File: libpthread
Tags: newcomer
It's possible I don't quite have the right package.
man pthread_init does not find a man page but should. I'm not certain but I think one can be thrown
together pretty quickly from the one on the open group.

You want the glibc-doc package. (The Open Group materials may not be
licensed appropriately, but it shouldn't be hard to put together a
manpage.)

[Debian Bug Tracking System]

Your message dated Wed, 14 Nov 2018 12:07:28 +0100
with message-id <decf8ea0-9752-c400-88ce-***@debian.org>
and subject line Re: [Xcb] Bug#912189: Bug#912189: libpthread: man pthread_mutex_init doesn't find a man page
has caused the Debian Bug report #912189,
regarding libpthread: man pthread_mutex_init doesn't find a man page
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)