General information
About
News
FAQ
Contact us
Documentation
How to file bugs
using templates
Debian policy
piuparts.d.o configuration:
piuparts.conf,
distros.conf
and scripts
README
README_server
piuparts manpage
Summaries
Bugs filed
Suites overview
Suite: sid
by maintainer / uploader
by source package
all tested suites
experimental
sid2experimental
sid
sid-strict
sid-nodoc
testing2sid
stable2sid
stable22sid
buster
buster-rcmd
stretch2buster
stretch2buster-rcmd
stretch2bpo2buster
stretch2bpo
stretch
stretch-rcmd
stretch-security
stretch-pu
stretch2proposed
oldstable222sid
oldstable22testing
jessie2stretch
jessie2Xstretch
jessie2stretch-rcmd
jessie2Xstretch-rcmd
jessie2bpo2stretch
jessie2bpo
jessie
jessie-rcmd
jessie-security
jessie-pu
jessie2proposed
wheezy2jessie
wheezy2jessie-rcmd
wheezy2bpo2jessie
wheezy2lts
wheezy
wheezy-security
wheezy-pu
squeeze2wheezy-lts
squeeze2wheezy
squeeze2bpo-sloppy
squeeze2bpo2wheezy
squeeze2squeeze-lts
squeeze
lenny2squeeze
src: piuparts
Source
piuparts.d.o bugs
piuparts bugs / ToDo
Other Debian QA efforts
Debian QA Group
Dose tools (former: EDOS)
Lintian
Debian Package Tracker
Ultimate Debian Database
jenkins.debian.net
ci.debian.net
Last update
2018-11-13 23:55 UTC
About piuparts.debian.org
piuparts is a tool for testing that .deb packages can be installed, upgraded, and removed without problems. piuparts is short for "package installation, upgrading and removal testing suite" and is a variant of something suggested by Tollef Fog Heen.
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.
A quick introduction is available in the piuparts README, and all the options are listed on the piuparts manpage.
Besides all the information provided here, there is some more information available on wiki.debian.org:
You can talk to us on #debian-qa on irc.debian.org (OFTC) or send an email on the piuparts development mailinglist. The best ways to contribute are to provide patches via GIT pull requests and/or to file bugs based on piuparts runs.
Since 2005 piuparts is run systematically on all packages in Debian, at first only on unstable. Today piuparts.debian.org is testing many suites by running piuparts in master/slave mode. This setup currently consists of three hosts: pejacevic.debian.org and piu-slave-bm-a.debian.org and piu-slave-ubc-01.debian.org:
  • pejacevic acts as the piuparts-master, which is responsible for scheduling test jobs to the slaves. The other main task is to generate the reports which are served via https://piuparts.debian.org.
  • piu-slave-bm-a runs four piuparts-slave instances, which then run piuparts itself.
  • piu-slave-ubc-01 also runs four piuparts-slave instances.
The first two of these hosts run as virtualized hardware on a nice cluster hosted at Bytemark and the last one runs virtualised at the University of British Columbia.
To learn more about this setup, follow the "Documentation" links in the navigation menu on the left. Read those READMEs. The piuparts configuration for all the different suite(-combination)s that are currently being tested is also linked there.
These pages are updated two to three times a day.
Bugs submitted which were found using piuparts