General information
About + News
Overview
FAQ
Source
piuparts.d.o bugs
piuparts bugs / ToDo
Contact us
Documentation
piuparts manpage
README_1st
README_server
piuparts.d.o configuration:
piuparts.conf,
distros.conf
and scripts
How to file bugs
Debian policy
Available reports
Bugs filed
experimental
sid2experimental
sid
sid-nodoc
testing2sid
jessie
wheezy2jessie
wheezy2bpo2jessie
wheezy2proposed
squeeze2wheezy-proposed
wheezy
squeeze2wheezy
squeeze2bpo-sloppy
squeeze2bpo2wheezy
squeeze
lenny2squeeze
by maintainer / uploader
by source package
Other Debian QA efforts
Debian QA Group
EDOS tools
Lintian
Package Tracking System
Ultimate Debian Database
jenkins.debian.net
Last update
2014-04-24 14:20 UTC
How to file bugs based on tests run on piuparts.debian.org
This page shall grow into a well written explaination how to file useful bugs fast. It assumes you are familar with reporting bugs in Debian.
First, of all, read the piuparts logfile and identify why piuparts testing failed.
Then, check the BTS for that package, to see if this issue was already filed as a bug. Often it's also useful to check the source packages bug page.
Then, if there is none, file a bug. If there already is a bug describing the same problem you're seeing in the piuparts logfile, usertag it like this:
 User: debian-qa@lists.debian.org
 Usertags: piuparts
	
This will make sure, piuparts.debian.org picks up your bug report (actually, it's piuparts-analyse.py) and marks it as bugged in the database.
Also, if you file a new bug report, don't forget to usertag it! The following is an example bug report. There are many more templates available for you to make use from!
 To: submit@bugs.debian.org
 Subject: $package: fails to upgrade from 'testing' - trying to overwrite ...

 Package: $package
 Version: $version
 Severity: serious
 User: debian-qa@lists.debian.org
 Usertags: piuparts

 Hi,

 during a test with piuparts I noticed your package fails to upgrade from
 'testing'. It installed fine in 'testing', then the upgrade to 'sid'
 fails because it tries to overwrite other packages files without
 declaring a replaces relation.

 See policy 7.6 at
 http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

 From the attached log (scroll to the bottom...):

 $useful_except_from_logfile

 cheers,
        $your_name

 attachment: $failed_logfile
	
Please take care when filing bugs to file meaningful bugs and to not annoy maintainers. Don't nitpick or insist on severities, the important thing is to get the bug fixed, not the right severity. Optionally you can also send copies to the piuparts-devel mailinglist by adding X-debbugs-cc: piuparts-devel@lists.alioth.debian.org pseudo-headers.
Also, you should be aware that what you are doing can probably be seen as mass bug filing (even if you just file a few now, they are part of a series of bugs of one kind) and as such needs to be discussed on debian-devel@lists.d.o first! For many types of bugs this has already been done. This is or should be indicated in the summary web pages as well as the mail templates.
Finally, besides simply usertagging a bug, piuparts-analyse understands more, and you can also do the following:
 # assume 987654 is our bug report in buggy-package,
 # but the problem only shows up when testing (upgrades of)
 # failing-package with piuparts:
 bts affects 987654 failing-package

 # and if failing-package is from a different source with a different
 # version number:
 bts found 987654 failing-package/$FAILED_VERSION