On Tue, Mar 20, 2001 at 12:55:42AM +0000, Colin Watson wrote: > >On a clean installation of Debian 2.2 when I man a program that doesn't > >have a man page I get stuff like > >man: warning: /usr/share/man/man1/resolveip.1.gz is a dangling symlink > >man: can't open /usr/share/man/man1/resolveip.1: No such file or directory > >man: warning: /usr/share/man/man1/resolveip.1.gz: bad symlink or ROFF > >`.so' request [etc.] > Only the maintainers of the packages in question can (respectively, > mysql-server and libqt2-dev). Dangling symlinks are usually a bug. I > have some stuff in the works to try to stop man rescanning quite so > much, though. A lot of those dangling symlinks are leftovers of a bad bug in update-alternatives (and thus in dpkg); for many years update-alternatives would not remove slave symlinks when an alternative was removed. And guess what? manpage symlinks are almost always slaves of the binary that is used as an alternative. -- G. Branden Robinson | One man's "magic" is another man's Debian GNU/Linux | engineering. "Supernatural" is a branden@debian.org | null word. http://www.debian.org/~branden/ | -- Robert Heinlein
Attachment:
pgpE7NEiElF6H.pgp
Description: PGP signature