RFH: handle bug reports for unknown packages
Over the years, with the help of Colin Watson and others, I've handled bug reports for packages that the BTS doesn't know about (either because the package was removed, is in some unofficial repo or because the bug submitter made a typo). I'm looking for someone to take over this activity. I've included more information below on what is involved. Anyone interested? P.S. Is there a good place in the wiki to add this job description. I think it would be worth to preserve it there for the future. (Please CC since I'm not subscribed to -qa) Job description: When a bug is filed in the BTS for a package that is not in the Debian archive, the bug report is sent to the QA unknown-package alias. The bug report then needs to be handled in an appropriate manner, e.g. reassigned to another package (for example when there's a typo in the package name) or closed (when the package no longer exists in the Debian archive). When a bug report for an unknown package comes in, the following information can be checked to decide what to do about the bug: - Check the NEW queue at http://ftp-master.debian.org/new.html and the incoming queue at http://incoming.debian.org The BTS doesn't know about packages in NEW or incoming but bug reports for such packages are worthwhile reports. You can simply bounce a copy of the bug report to the maintainer or reply to the bug and put the maintainer in CC. - Check the list of removed packages at http://ftp-master.debian.org/removals-full.txt If the package was removed from Debian, you can close the bug report saying that the package was removed and why it was removed. - Check the Content file to see if the unknown package name is a valid in an existing package. - Often the package name in the bug report is an obvious typo for an existing package. In that case, you can simply reassign the bug, ideally with a version number (reassign n package version). - We often get bug reports for linux-image-2.6.xx* packages that no longer exist. They should be reassigned to the linux-2.6 package since they might still be relevant. - We also get a lot of bug reports for packages in the unofficial Debian Multimedia repository at debian-multimedia.org. The best way to handle such reports is to CC the debian-multimedia.org maintainer, Christian Marillat , and close them with a message that debian-multimedia.org is not an official repo and that you have copied the maintainer. - Finally, if you don't know where the package comes from, you can ask the submitter. Suggest that they run: dpkg -p PACKAGE | grep Maintainer: to see who the maintainer is. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110529101628.ga32...@jirafa.cyrius.com
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/ -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110529102743.ga32...@jirafa.cyrius.com
Re: RFH: handle bug reports for removed packages
On Sun, May 29, 2011 at 6:27 PM, Martin Michlmayr wrote: > 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? IIRC the FTP masters took over at least part of this. For eg: http://bugs.debian.org/596536 -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi�4-qa_c05nzjm55tkqwbyzq...@mail.gmail.com
Re: RFH: handle bug reports for removed packages
Given I already did this kind of work in the past, I think I can keep doing that. cheers, Sandro On Sun, May 29, 2011 at 10:27, Martin Michlmayr wrote: > 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/ > > > -- > To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20110529102743.ga32...@jirafa.cyrius.com > > -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikf==ivf-ygl9dvk69l8hotjmn...@mail.gmail.com
Re: RFH: handle bug reports for removed packages
On Sun, May 29, 2011 at 10:52, Paul Wise wrote: > On Sun, May 29, 2011 at 6:27 PM, Martin Michlmayr wrote: > >> 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? > > IIRC the FTP masters took over at least part of this. For eg: > > http://bugs.debian.org/596536 Only for the new RM, not for the ancient removals (and sometimes I see packages removed with bugs still opened, but didn't dive deep into the issue). -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktikzf1qfxntg2v2npqwdvdm1qrv...@mail.gmail.com
Re: RFH: handle bug reports for unknown packages
I can probably take over this too. Sandro On Sun, May 29, 2011 at 10:16, Martin Michlmayr wrote: > Over the years, with the help of Colin Watson and others, I've handled > bug reports for packages that the BTS doesn't know about (either > because the package was removed, is in some unofficial repo or because > the bug submitter made a typo). I'm looking for someone to take over > this activity. I've included more information below on what is > involved. > > Anyone interested? > > P.S. Is there a good place in the wiki to add this job description. > I think it would be worth to preserve it there for the future. > > (Please CC since I'm not subscribed to -qa) > > > Job description: > > When a bug is filed in the BTS for a package that is not in the Debian > archive, the bug report is sent to the QA unknown-package alias. The > bug report then needs to be handled in an appropriate manner, e.g. > reassigned to another package (for example when there's a typo in the > package name) or closed (when the package no longer exists in the Debian > archive). > > When a bug report for an unknown package comes in, the following > information can be checked to decide what to do about the bug: > > - Check the NEW queue at http://ftp-master.debian.org/new.html and > the incoming queue at http://incoming.debian.org The BTS doesn't > know about packages in NEW or incoming but bug reports for such > packages are worthwhile reports. You can simply bounce a copy of > the bug report to the maintainer or reply to the bug and put the > maintainer in CC. > > - Check the list of removed packages at > http://ftp-master.debian.org/removals-full.txt > If the package was removed from Debian, you can close the bug report > saying that the package was removed and why it was removed. > > - Check the Content file to see if the unknown package name is a valid > in an existing package. > > - Often the package name in the bug report is an obvious typo for an > existing package. In that case, you can simply reassign the bug, > ideally with a version number (reassign n package version). > > - We often get bug reports for linux-image-2.6.xx* packages that no > longer exist. They should be reassigned to the linux-2.6 package > since they might still be relevant. > > - We also get a lot of bug reports for packages in the unofficial > Debian Multimedia repository at debian-multimedia.org. The best > way to handle such reports is to CC the debian-multimedia.org > maintainer, Christian Marillat , and close > them with a message that debian-multimedia.org is not an official > repo and that you have copied the maintainer. > > - Finally, if you don't know where the package comes from, you can ask > the submitter. Suggest that they run: > dpkg -p PACKAGE | grep Maintainer: > to see who the maintainer is. > > -- > Martin Michlmayr > http://www.cyrius.com/ > > > -- > To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20110529101628.ga32...@jirafa.cyrius.com > > -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi=pqixd0mk9s3r7rkti6aqncjr...@mail.gmail.com
Bug#628523: Don't be so sure about piuparts
Package: qa.debian.org Severity: minor The page says: "Piuparts found an (un)installation error in the Sid version of this package. You should fix it; " But piuparts gives many false positives and has no override mechanism, so in many cases there is nothing to fix. So please don't say "You should fix it." Say, "You should investigate the cause." Or something appropriately weak. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimfnsico_4u4g0egwnsbjvacu1...@mail.gmail.com
