back to piuparts.debian.org


piuparts.debian.org: Frequently Asked Questions

Q. piuparts logs are long and cluttered with debug output - how do you read them?
A) Usually it's best to read them bottom up, as errors happen at the end.
Q. Whom should I contact if I think I found a false positive?

A) debian-qa@lists.debian.org - but please read the complete FAQ before doing so.

Q. How can I help?

A) by filing lots of bugs ;-) Please use piuparts usertags, to be written/copied templates for the bugreports and please get in touch with debian-qa@lists.debian.org too. Mid-term plan is to write tools to ease mass bug-reporting.

Q. What are circular dependencies?

A) perl depends on perl-modules and perl-modules depends on perl. That's an easy one. The more annoying ones are those from different source packages.

Q. What does state ''unknown-package-or-udeb'' mean?
A) Just by looking at the Packages and Sources files it's impossible to distinguish unknown packages (because they haven't build yet are only available on certains archs) and udebs, so that's why the state is so ambiguous. Future versions of piuparts-report are supposed to alse parse the Packages files in the debian-installer directories, making it possible to properly detect udebs.
Q. Do you plan to test other architectures?
A) Yes. (Look at the file TODO in svn trunk.)
Q. I'd like to fix a bug in piuparts - where is the code?

A) svn://svn.debian.org/svn/piuparts/trunk has the piuparts source code, while svn://svn.debian.org/svn/piuparts/piatti is the code being run piatti.debian.org to produce http://piuparts.debian.org.


CategoryPermalink