RFH: handle bug reports for removed packages
I'm looking for someone to take care of bugs of packages that have
been removed from Debian. More information on the task is below.
Anyone interested?
Note: I stopped taking care of such bug reports a fairly long time
ago, so there's a lot of bugs that need to be processed right now.
(Please CC since I'm not subscribed to -qa)
Job description:
When a package is removed from Debian, bugs associated with this
package are not automatically closed or reassigned. While it's
normally the job of the maintainer to take care of these bugs,
this is often not done in practice and so QA needs to take care
of these bug reports.
Here is some information about this task:
- When a package is removed because of a newer version (this is
common with libraries and the kernel), it may be appropriate
to reassign the bug to the new package.
- When an old release of Debian is removed from the archive, a
lot of bug reports lose their maintainer information since the
BTS no longer knows how to associate the bug report with the
package maintainer. Such bugs are usually very old. It may be
appropriate to close these bugs with a message saying that this
release of Debian is no longer supported and that they should
file a new bug or let you know if the bug still exists in the
current version of Debian.
- When in doubt what to do, ask the maintainer how to handle the
bugs or ask them to take care of it.
- When closing a bug of a removed package, the best way is to done
a message to -done and to include a Version header that is
slightly higher than the last version in the archive (e.g. 1.0-1+rm
for 1.0-1).
- A QA alias removed-packages exists which receives a notification
whenever a package is removed by the FTP masters.
- Bug reports that don't have a maintainer associated with it can
be found at http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=&pend-exc=absent&pend-exc=done
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: