Differences between revisions 13 and 14
Revision 13 as of 2009-05-12 10:12:19
Size: 2761
Editor: HolgerLevsen
Comment: i love the smell of syntax errors at noon
Revision 14 as of 2009-05-12 19:18:55
Size: 3018
Editor: HolgerLevsen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 Q. A package I'm interested in is in an untestable state. How can I find out if it would pass the piuparts test? :: A) [[http://piuparts.debian.org/doc/README.html#_how_to_use_piuparts_in_5_minutes||Run piuparts manually]], as described in that README.

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. What does a depends of ''circular dependency'' mean?

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. Some packages (for example [[http://piuparts.debian.org/sid/source/i/ilohamail.html|ilohamail]]) are in the state ''dependency-does-not-exist'', but they have resolvable depends, they just also have unresolvable depends. Why?
A) That's a bug in piuparts.
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. So there are quite some issues in the piuparts webpages (just look at the previous three questions), shouldn't you first fix them before announcing piuparts.debian.org widely?
A) No. piuparts.debian.org is already very useful to detect problems and to file bugs. Once those bugs are filed (and fixed) it makes more sense to investigate those packages which cannot be tested at the moment.
Q. A package I'm interested in is in an untestable state. How can I find out if it would pass the piuparts test?

A) http://piuparts.debian.org/doc/README.html#_how_to_use_piuparts_in_5_minutes, as described in that README.

Q. Do you plan to test other architectures?
A) Yes. (Look at the file TODO in svn trunk.)
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. 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. See the piuparts wiki page for more information on how to help developing piuparts.


CategoryPermalink