Your message dated Sat, 25 Jul 2009 10:53:55 +0000
with message-id <e1muet1-000643...@ries.debian.org>
and subject line Bug#535986: fixed
has caused the Debian Bug report #535986,
regarding RM: dak -- RoQA; old, unmaintained, 6 NMUs, unusable as-is
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 ow...@bugs.debian.org
immediately.)
--
535986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dak
Version: 1.0-8.4
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal
Hi Joerg and James,
I have a script that finds packages which are good candidates to be
orphaned or removed from Debian, and dak came up.
I was wondering what's the status of the dak package. I don't think that
it's still in sync with the dak which is used in the Debian
infrastructure.
Is the dak package still useful as is?
Furthermore, the package has a number of unanswered RC bugs, has a low
popcon, and has not been in testing for nearly a year.
Wouldn't it be better to just remove the dak package from Debian, until
someone has time to package the current version?
Thank you,
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
dak | 1.0-8.6 | source, hurd-i386, kfreebsd-amd64, kfreebsd-i386
dak | 1.0-8.6+b1 | alpha, amd64, armel, hppa, i386, ia64, mips, mipsel,
powerpc, s390, sparc
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.
Packages are never removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.
Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System. Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 535...@bugs.debian.org.
The full log for this bug can be viewed at http://bugs.debian.org/535986
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.
Debian distribution maintenance software
pp.
Mark Hymers (the ftpmaster behind the curtain)
--- End Message ---
