reassign 162510 dpkg,elvis thanks [Jerome, please make sure to mail the bug report number as well as me.]
On Fri, Sep 27, 2002 at 11:58:31PM -0400, Jerome Acks Jr wrote: > On Fri, Sep 27, 2002 at 02:00:30PM +0100, Colin Watson wrote: > > On Thu, Sep 26, 2002 at 08:18:59PM -0400, Jerome Acks Jr wrote: > > > After upgrading exuberant-ctags to 5.3-1 on 23 Sep 200 2, I am now > > > getting the following warning: > > > > > > /etc/cron.daily/man-db: > > > mandb: warning: /usr/share/man/man1/ctags.1.gz is a dangling symlink > > > > > > This may be related to bug# 160957. > > > > Yeah, I need to get round to replying to that. > > > > > # ls -l /usr/share/man/man1/ctags.1.gz > > > lrwxrwxrwx 1 root root 28 Nov 25 2000 > > > /usr/share/man/man1/ctags.1.gz -> /etc/alternatives/ctags.1.gz > > > > What does /etc/alternatives/ctags.1.gz point to? > > ls -l /etc/alternatives/ctags.1.gz > lrwxrwxrwx 1 root root 30 May 19 2001 > /etc/alternatives/ctags.1.gz -> /usr/man/man1/ctags-elvis.1.gz Taking into account the fact that ctags-elvis doesn't appear anywhere in your /var/lib/dpkg/alternatives/ctags, this would appear to be a bug in either dpkg (for update-alternatives) or elvis. /etc/alternatives/ctags.1.gz should definitely not still be pointing to /usr/man/man1/ctags-elvis.1.gz, and this feels like a bug in update-alternatives itself. However, there may be a bug in elvis' use of alternatives or its handling of the upgrade. Unfortunately I don't grok update-alternatives enough to say for sure, so I'll have to pass this over to others. My best guess is that the only involvement of exuberant-ctags was in it installing its own alternative for ctags, which prodded update-alternatives into changing its automatic links. > $ man etags > man: bad fetch on multi key 1 1emacs21 > man: index cache /var/cache/man/index.bt corrupt > > $ man ctags > man: warning: /usr/share/man/man1/ctags.1.gz is a dangling symlink > man: bad fetch on multi key 1 1emacs21 > man: index cache /var/cache/man/index.bt corrupt That would appear to be bug #159451. Make sure you have man-db 2.4.0-7 or later, and check man-db's Debian changelog for instructions on fixing (i.e. recreating) databases affected by the bug. Cheers, -- Colin Watson [EMAIL PROTECTED]
