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.

piuparts itself has a README_1st and a manpage, for the piuparts.debian.org setup there is also an FAQ available.

Useful links for piuparts development

• Alioth project: https://alioth.debian.org/projects/piuparts/

• Source code:

  • Browse it: http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git

  • Get it: git clone git://anonscm.debian.org/piuparts/piuparts.git

  • Github: https://github.com/h01ger/piuparts

• Mailinglists:

  • Development: piuparts-devel@l.a.d.o

  • Commit diffs list: piuparts-commits@l.a.d.o

• TODO

• PTS page

• Known bugs

Advanced usage tips for piuparts

• This obviously implies you are familar with the manpage, README_1st and README_server :-D

• piuparts/UseCases

Ressources about piuparts.debian.org & distributed testing

• piuparts.d.o reports list: piuparts-reports@l.a.d.o

• README_server

• README_pejecevic.txt - information how the setup has been made together with DSA.

• 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)

• instances/piuparts.conf.anbe

• instances/piuparts.conf.goldwasser

Old 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

CategoryPermalink