Your message dated Thu, 21 Sep 2006 20:29:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388636: cron.daily/man-db to clean up dangling symlinks
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: man-db
Version: 2.4.3-3
Severity: wishlist
File: /etc/cron.daily/man-db
Idea: /etc/cron.daily/man-db could also clean up dangling symlinks.
It seems the problem comes up so often (every apt-get upgrade. A
different package causing the problem each time) that there might as
well be a cron job to clean them up.
>> I forgot what I should do in this case
>>
>> >>>>> "A" == Anacron <[EMAIL PROTECTED]> writes:
>>
A> /etc/cron.daily/man-db:
A> mandb: warning: /usr/share/man/man1/cc.1.gz is a dangling symlink
A> mandb: warning: /usr/share/man/man1/c++.1.gz is a dangling symlink
>>
>> $ reportbug -f /usr/share/man/man1/c++.1.gz
>> No packages match.
>> $ reportbug -f /usr/share/man/man1/cc.1.gz
>> No packages match.
C> Figure out what package left the dangling alternative lying around on
C> removal (ask debian-user@ or something for help if need be), and file a
This will only anger people more.
C> bug against it. Since multiple packages provide these symlinks via
C> update-alternatives, only you can figure out which one left it behind on
C> your system (e.g. by studying /var/log/dpkg.log).
Urggg... I get dizzy each time I loop around update-alternatives and
... well ... I'm not as brainy as I used to be.
--- End Message ---
--- Begin Message ---
On Thu, Sep 21, 2006 at 10:59:07PM +0800, Dan Jacobson wrote:
> Package: man-db
> Version: 2.4.3-3
> Severity: wishlist
> File: /etc/cron.daily/man-db
>
> Idea: /etc/cron.daily/man-db could also clean up dangling symlinks.
I really don't think it's the job of that task to go around removing
random filesystem nodes, and I think that would be a bad thing. It
should be possible to run most of it with reduced privileges. (In fact,
I expect the SELinux lot are already doing so.)
> It seems the problem comes up so often (every apt-get upgrade. A
> different package causing the problem each time) that there might as
> well be a cron job to clean them up.
They're all bugs, and bugs should be fixed, not have their debris
cleaned up by a cron job.
> C> Figure out what package left the dangling alternative lying around on
> C> removal (ask debian-user@ or something for help if need be), and file a
>
> This will only anger people more.
I'm afraid that can only be a problem with your approach, then. I've
never had any problem reporting this kind of bug, or asking for help
about it.
> C> bug against it. Since multiple packages provide these symlinks via
> C> update-alternatives, only you can figure out which one left it behind on
> C> your system (e.g. by studying /var/log/dpkg.log).
>
> Urggg... I get dizzy each time I loop around update-alternatives and
> ... well ... I'm not as brainy as I used to be.
I'm sorry, but I can't help with that - not even via a bug report.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--- End Message ---
