tags 441203 fixed-upstream
thanks

Some of these were fixed in 2.64, the rest have already been
fixed for the upcoming 2.65.

Thanks,

Michael


Paulo Marcel Coelho Aragão wrote:
> Package: manpages-dev
> Version: 2.63-1
> Severity: normal
> 
> The following symlinks are dangling:
> 
> /usr/share/man/man2/mq_notify.2.gz -> mq_notify.3.gz
> /usr/share/man/man2/mq_open.2.gz -> mq_open.3.gz
> /usr/share/man/man2/mq_timedreceive.2.gz -> mq_receive.3.gz
> /usr/share/man/man2/mq_timedsend.2.gz -> mq_send.3.gz
> /usr/share/man/man2/mq_unlink.2.gz -> mq_unlink.3.gz
> /usr/share/man/man2/oldfstat.2.gz -> stat2.2.gz
> /usr/share/man/man2/oldlstat.2.gz -> stat2.2.gz
> /usr/share/man/man2/oldstat.2.gz -> stat2.2.gz
> 
> I suppose they should be:
> 
> /usr/share/man/man2/mq_notify.2.gz -> ../man3/mq_notify.3.gz
> /usr/share/man/man2/mq_open.2.gz -> ../man3/mq_open.3.gz
> /usr/share/man/man2/mq_timedreceive.2.gz -> ../man3/mq_receive.3.gz
> /usr/share/man/man2/mq_timedsend.2.gz -> ../man3/mq_send.3.gz
> /usr/share/man/man2/mq_unlink.2.gz -> ../man3/mq_unlink.3.gz
> /usr/share/man/man2/oldfstat.2.gz -> stat.2.gz
> /usr/share/man/man2/oldlstat.2.gz -> stat.2.gz
> /usr/share/man/man2/oldstat.2.gz -> stat.2.gz
> 
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages manpages-dev depends on:
> ii  manpages                      2.63-1     Manual pages about using a 
> GNU/Lin
> 
> manpages-dev recommends no packages.
> 
> -- no debconf information
> 
> 

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7

Want to help with man page maintenance?  Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages/
read the HOWTOHELP file and grep the source files for 'FIXME'.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to