Differences between revisions 1 and 93 (spanning 92 versions)
Revision 1 as of 2006-12-18 12:51:51
Size: 494
Editor: HolgerLevsen
Comment:
Revision 93 as of 2014-05-20 11:36:33
Size: 1885
Editor: HolgerLevsen
Comment: small is more
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= general info = #language en
Line 3: Line 3:
piuparts runs on piuparts.cs.helsinki.fi aka piatti.debian.org. === What is piuparts? ===
Line 5: Line 5:
#debian-qa is the irc-channel to coordinate work on irc, piuparts-devel is the project name on alioth. {{{
Description: .deb package installation, upgrading, and removal testing tool
 piuparts tests that .deb packages (as used by Debian) handle
 installation, upgrading, and removal correctly. It does this by
 creating a minimal Debian installation in a chroot, and installing,
 upgrading, and removing packages in that environment, and comparing the
 state of the directory tree before and after. piuparts reports any
 files that have been added, removed, or modified during this process.
 .
 piuparts is meant as a quality assurance tool for people who create .deb
 packages to test them before they upload them to the Debian package archive.
Homepage: https://piuparts.debian.org
}}}
Line 7: Line 19:
= how to run piuparts = === piuparts.debian.org ===
Line 9: Line 21:
the piuparts stuff is partly in the piupartsm account (master end, including debmirroring), and partly in the piuartss account (the slave, which actually runs piuparts) piuparts is being run constantly on all suites of the main Debian archive, the results are made public on [[https://piuparts.debian.org|piuparts.debian.org]].
The [[piuparts/piuparts.debian.org|piuparts.debian.org setup]] is documented and maintained in GIT, plus there is also an [[piuparts/FAQ|FAQ]] available.
Line 11: Line 24:
also read http://liw.iki.fi/liw/debian/piuparts-logfile-processing-howto === Documentation ===
Line 13: Line 26:
piuparts itself has a [[https://piuparts.debian.org/doc/README_1st.html|README_1st]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|manpage]] - read those before reading the [[piuparts/HowTos]].
Line 14: Line 28:
.. to be continued... === Contributing ===

If you are interested in contributing, that's great! Here's a list to hopefully get you started:
 * join [[piuparts/Development|development]] efforts. Every little pull request helps. Check the BTS for plenty of wishlist bugs to tackle.
 * [[https://piuparts.debian.org/bug_howto.html|file bugs]] based on piuparts.d.o runs!
 * improve the documentation, both these wiki pages and what's in GIT has been growing over the years and it's showing.

----
## This page is referenced from http://piuparts.debian.org
CategoryPermalink

What is piuparts?

Description: .deb package installation, upgrading, and removal testing tool 
 piuparts tests that .deb packages (as used by Debian) handle
 installation, upgrading, and removal correctly. It does this by
 creating a minimal Debian installation in a chroot, and installing,
 upgrading, and removing packages in that environment, and comparing the
 state of the directory tree before and after. piuparts reports any
 files that have been added, removed, or modified during this process.
 .
 piuparts is meant as a quality assurance tool for people who create .deb
 packages to test them before they upload them to the Debian package archive.
Homepage: https://piuparts.debian.org

piuparts.debian.org

piuparts is being run constantly on all suites of the main Debian archive, the results are made public on piuparts.debian.org. The piuparts.debian.org setup is documented and maintained in GIT, plus there is also an FAQ available.

Documentation

piuparts itself has a README_1st and a manpage - read those before reading the piuparts/HowTos.

Contributing

If you are interested in contributing, that's great! Here's a list to hopefully get you started:

  • join development efforts. Every little pull request helps. Check the BTS for plenty of wishlist bugs to tackle.

  • file bugs based on piuparts.d.o runs!

  • improve the documentation, both these wiki pages and what's in GIT has been growing over the years and it's showing.


CategoryPermalink