On 25/04/08 at 14:35 +0700, Martin Michlmayr wrote: > > http://qa.debian.org/~lucas/bapase/bugs_rm_pkgs.txt (updated every 6 hours). > > This script lists bugs that: > > - are not marked as done > > - don't affect testing, unstable or experimental > > - don't belong to a package in testing, unstable or experimental > > This is only a list of good candidates. Many of those bugs shouldn't be > > closed! > > Yep, in particular, this will also include bugs that were filed > against an unknown package (for example because of a typo in the > package name). I still take care of these bugs as they come in, but I > always miss some so it would be good if I could easily see bugs that > are not open bugs from removed packages. (In the past, I would close > or reassign all bugs from removed packages, and then load the BTS page > for bugs without a maintainer and reassign/close those until the page > is empty. But with the current backlog of open bugs from removed > packages, this BTS page is way too long to be usable.)
I added a note about this case in the README file. > Do you think you could add one optional step to bugs_rm_pkgs.rb: > exclude all bugs from packages that are listed in the removals.txt > file. You could generate a file bugs_unknown_pkgs.txt and then I > could go through them. Is there a machine-parsable version of removals.txt? It's not exactly fun to parse. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]