|
Size: 1549
Comment:
|
Size: 1438
Comment: move to piuparts/piuparts.debian.org
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = general info = | #language en |
| Line 3: | Line 3: |
| piuparts runs on piuparts.cs.helsinki.fi aka piatti.debian.org and just like lintian and linda should be run on every developer machine before uploading :) | <<TableOfContents(2)>> |
| Line 5: | Line 5: |
| piuparts logs (currently outdated) are available at [http://piatti.debian.org http://piatti.debian.org] | = Overview about piuparts = |
| Line 7: | Line 7: |
| #debian-qa is the irc-channel to coordinate work on irc, piuparts-devel is the project name on alioth. | {{{ 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: |
| = how to run piuparts on piatti = | 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: |
| the piuparts stuff is partly in the piupartsm account (master end, including debmirroring), and partly in the piuartss account (the slave, which actually runs 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: |
| run piuparts-slave.py as piupartss and watch it run via screen. the slave starts the master when it needs it, you don't need to start it manually | = Advanced usage tips for piuparts = * This obviously implies you are familar with the manpage, README_1st and README_server :-D * [[piuparts/UseCases]] |
| Line 15: | Line 29: |
| also read http://liw.iki.fi/liw/debian/piuparts-logfile-processing-howto If you want to help, please don't bother liw, h01ger has access too and you should bother him. ... to be continued! ... = troubleshouting/maintainance = Sometimes the chroot tarballs in /home/piupartss/ need to be removed, currently there are sid.tar.gz and sarge.tar.gz see /etc/piuparts/piuparts-slave.conf = developing piuparts = * alioth project * http://wiki.debian.org/SummerOfCode2007/PiupartsImprovements = random todo-stuff = * split /fails/ into more directories * <liw> (at some point) you may want to run as piupartsm the bin/mirror-debian script * look at the irssi_away script to see how to monitor screen sessions, to notify when piuparts is hanging * backup /etc (and?) |
---- ## This page is referenced from http://piuparts.debian.org CategoryPermalink |
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