Your message dated Wed, 4 Jul 2012 13:19:04 +0100
with message-id
<CAPQ4b8kH0+w8OfoKoA5=pyhmqu8k5fvkkztoi3cipw7k_az...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (misdn-related packages)
has caused the Debian Bug report #360455,
regarding misdn-modules-2.6.16-1-486: leaves /lib/modules/2.6.16-1-486 on disk
after purged
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 [email protected]
immediately.)
--
360455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360455
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: misdn-modules-2.6.16-1-486
Version: 0.0.0+cvs20060214-1
When testing misdn-modules-2.6.16-1-486 with piuparts, I get the
following error:
0m5.9s ERROR: Package purging left files on system:
/lib/modules/2.6.16-1-486
owned by: misdn-modules-2.6.16-1-486
When the package is being purged, dpkg says:
0m5.2s DEBUG: Starting command: chroot /tmp/tmppt5tDV dpkg --purge
misdn-modules-2.6.16-1-486
0m5.2s DUMP: (Reading database ... 6951 files and directories
currently installed.)
0m5.2s DUMP: Removing misdn-modules-2.6.16-1-486 ...
0m5.2s DUMP: Purging configuration files for
misdn-modules-2.6.16-1-486 ...
0m5.2s DUMP: dpkg - warning: while removing
misdn-modules-2.6.16-1-486, directory `/lib/modules/2.6.16-1-486' not
empty so not removed.
--
Do, or do not. There is no angst.
--- End Message ---
--- Begin Message ---
Hello,
Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved in due time.
misdn packages have been recently removed from experimental [1], they
had been removed from unstable a few years ago [2].
[1] http://packages.qa.debian.org/m/misdn-kernel/news/20120627T165811Z.html
[2] http://packages.qa.debian.org/m/misdn-kernel/news/20071201T181403Z.html
The bugs are now orphan (without maintainer assigned) so they probably
will not be noticed/modified further. So I think that the best
solution is to close them now, doing it. Please comment if you want
to handle the reports in some other way (reassigned to other packages,
etc.).
Cheers.
--- End Message ---
