Overview about 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: http://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.
Useful links for piuparts development
Alioth project: https://alioth.debian.org/projects/piuparts/
- Source code:
Get it: git clone git://anonscm.debian.org/piuparts/piuparts.git
Advanced usage tips for piuparts
- This obviously implies you are familar with the manpage, README_1st and README_server :-D
Ressources about piuparts.debian.org & distributed testing
piuparts.d.o reports list: firstname.lastname@example.org
instances/piuparts.conf.pejacevic is installed as /etc/piuparts/piuparts.conf on both the host acting as master as well as the slave.
conf/distros.conf is installed as /etc/piuparts/distros.conf (also on all hosts).
custom-scripts are installed into /etc/piuparts/scripts (also on all hosts).
Old(er) development efforts
There was a SummerOfCode2007/PiupartsImprovements.
Code analysis and more on ohloh (needs update).
- 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