Differences between revisions 89 and 90
⇤ ← Revision 89 as of 2013-06-02 22:09:15 →
Size: 4083
Editor: HolgerLevsen
Comment: .
← 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 25: Line 25:
= 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: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-devel|piuparts-devel@l.a.d.o]]
  * Commit diffs 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]]
Line 54: Line 40:
= Old(er) 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

Contents

  1. Overview about piuparts
  2. Advanced usage tips for piuparts
  3. Ressources about piuparts.debian.org & distributed testing

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