Differences between revisions 76 and 90 (spanning 14 versions)
Revision 76 as of 2013-06-01 15:10:23
Size: 2086
Editor: HolgerLevsen
Comment: fix list
Revision 90 as of 2014-05-20 11:13:23
Size: 2766
Editor: HolgerLevsen
Comment: move to piuparts/Development
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
{{{ Description: .deb package installation, upgrading, and removal testing tool }}} {{{
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
}}}
Line 9: Line 21:
piuparts is being run constantly on the main archive, the results are public on [[http://piuparts.debian.org|piuparts.debian.org]]. piuparts itself has a [[http://piuparts.debian.org/doc/README_1st.html|README_1st]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|piuparts manpage]], for the piuparts.debian.org setup there is also an [[http://wiki.debian.org/piuparts/FAQ|FAQ]] available. Below is an overview of information not covered elsewhere. piuparts is being run constantly on all suites of the main Debian archive, the results are made public on [[http://piuparts.debian.org|piuparts.debian.org]].
Line 11: Line 23:
= Developing piuparts = piuparts itself has a [[http://piuparts.debian.org/doc/README_1st.html|README_1st]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|manpage]], for the piuparts.debian.org setup there is also an [[http://wiki.debian.org/piuparts/FAQ|FAQ]] available.
Line 13: Line 25:
 * 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: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-devel|piuparts-devel@l.a.d.o]]
  * commit diff list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-commits|piuparts-commits@l.a.d.o]]
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=TODO;hb=develop|TODO]]
= Advanced usage tips for piuparts =
 * This obviously implies you are familar with the manpage, README_1st and README_server :-D
 * [[piuparts/UseCases]]
Line 19: Line 29:
== Old development efforts == = Ressources about piuparts.debian.org & distributed testing =
Line 21: Line 31:
 * there was a [[SummerOfCode2007/PiupartsImprovements]]
 * [[http://www.ohloh.net/p/9038|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

= More ressources =
 * piuparts.d.o reports list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-reports|piuparts-reports@l.a.d.o]]
Line 33: Line 33:
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=READNE_pejecevic.txt;hb=HEAD|README_pejecevic.txt]]
 * piuparts.conf.anbe
 * piuparts.conf.goldwasser
 * [[piuparts/UseCases]]
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=README_pejacevic.txt;hb=HEAD|README_pejecevic.txt]] - information how the setup has been made together with [[Teams/DSA|DSA]].
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=instances/piuparts.conf.pejacevic|instances/piuparts.conf.pejacevic]] is installed as /etc/piuparts/piuparts.conf on both the host acting as master as well as the slave.
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=conf/distros.conf|conf/distros.conf]] is installed as /etc/piuparts/distros.conf (also on all hosts).
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=tree;f=custom-scripts|custom-scripts]] are installed into /etc/piuparts/scripts (also on all hosts).
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=instances/piuparts.conf.anbe|instances/piuparts.conf.anbe]]
 * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=instances/piuparts.conf.goldwasser|instances/piuparts.conf.goldwasser]]

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.

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


CategoryPermalink