|
Size: 2557
Comment:
|
Size: 2766
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 all suites of the main Debian archive, the results are made public on [[http://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 [[http://piuparts.debian.org|piuparts.debian.org]]. |
| Line 13: | Line 25: |
| = Useful links for piuparts development = * alioth project: [[https://alioth.debian.org/projects/piuparts/]] * source code: * Browse it: [[https://alioth.debian.org/scm/browser.php?group_id=30965]] * Get it: `git clone git://anonscm.debian.org/piuparts/piuparts.git` * Github: https://github.com/h01ger/piuparts * mailinglists: * development: [[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]] * [[http://packages.qa.debian.org/piuparts|PTS page]] * [[http://bugs.debian.org/src:piuparts|Known bugs]] in piuparts = More ressources for using piuparts = * [[http://piuparts.debian.org/doc/README_server.html|README_server]] * piuparts.conf.anbe * piuparts.conf.goldwasser |
= Advanced usage tips for piuparts = * This obviously implies you are familar with the manpage, README_1st and README_server :-D |
| Line 34: | Line 29: |
| = More ressources about piuparts.debian.org = | = Ressources about piuparts.debian.org & distributed testing = |
| Line 36: | Line 31: |
| * piuparts.d.o reports list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-reports|piuparts-reports@l.a.d.o]] * [[http://piuparts.debian.org/doc/README_server.html|README_server]] |
|
| Line 37: | Line 34: |
| * piuparts.d.o reports list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-reports|piuparts-reports@l.a.d.o]] = Old development efforts = * there was a [[SummerOfCode2007/PiupartsImprovements]] * [[http://www.ohloh.net/p/9038|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 |
* [[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]] |
Contents
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
Ressources about piuparts.debian.org & distributed testing
piuparts.d.o reports list: piuparts-reports@l.a.d.o
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).