Contents
Overview about piuparts
Description: .deb package installation, upgrading, and removal testing tool
piuparts is being run constantly on the main archive, the results are public on piuparts.debian.org. piuparts itself has a README and a piuparts manpage, for the piuparts.debian.org setup there is also an FAQ available. Below is an overview of information not covered elsewhere.
Developing piuparts
alioth project: https://alioth.debian.org/projects/piuparts/
source code: Browse: https://alioth.debian.org/scm/browser.php?group_id=30965 Get: git clone git://anonscm.debian.org/piuparts/piuparts.git
mailing list: piuparts-devel@l.a.d.o
commit diff list: piuparts-commits@l.a.d.o
- todo
Old development efforts
there was a SummerOfCode2007/PiupartsImprovements
code analysis and more on ohloh
- Developing piuparts, the rewrite of version 2
- stalled at planning stage
in bzr: bzr get http://code.liw.fi/piuparts2/bzr/trunk/ (may move to bzr.debian.org later)
- From the BoF at Debconf9
new output format: http://lists.debian.org/debian-devel/2009/07/msg00662.html
- piuparts should not fail just because dependencies fail
How piuparts is setup on piuparts.debian.org
Running piuparts is the boring, automated part and is supervised by Luk and Holger, who can su into the piupartss (slave) user. piuparts-slave is run in a shared screen session and seldom needs interaction. The piupartss user needs to be able to run piuparts and thus can use sudo without restrictions.
The slave automatically starts the master, to reserve packages to process and to pass logfiles to the master.
Ideally all members of the Debian-QA group can su to the piupartsm user and process the logfiles - currently it's again only Luk and Holger. piupartsm has no special privileges. If you want to help, please join #debian-qa and say so there.
Once a day piuparts-reports is run as piupartsm by cron to generate the html output of the logs.
For more information see http://anonscm.debian.org/gitweb/?p=piuparts/piatti.git;a=blob;f=README.txt;hb=HEAD