|
Size: 2299
Comment:
|
Size: 1911
Comment: fix broken link to README (pointing to a rendered version would be better, though)
|
| 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 :) piuparts logs (currently outdated) are available at [http://piatti.debian.org http://piatti.debian.org] #debian-qa is the irc-channel to coordinate work on irc, piuparts-devel is the project name on alioth. = how to run piuparts on piatti = 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) 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 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?) * also use the machine to run vlosuts = piuparts and pts integration suggestion = In order for the PTS to be able to display piuparts testing status for a package, and link to its log file, Piuparts could generate a set of static files that will be visible via http: |
=== What is piuparts? === |
| Line 46: | Line 6: |
| %s = source package name %v = source package version %p = piuparts version |
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: https://piuparts.debian.org }}} |
| Line 50: | Line 19: |
| /source/%s -> index page /source/%s/%v -> a particular log /source/%s/latest -> log for latest version /source/%s/piuparts-%p/%v -> a particular log from a version of piuparts |
=== piuparts.debian.org === |
| Line 55: | Line 21: |
| similar for /binary-$ARCH/ | piuparts is being run constantly on all suites of the main Debian archive, the results are made public on [[https://piuparts.debian.org|piuparts.debian.org]]. The [[piuparts/piuparts.debian.org|piuparts.debian.org setup]] is documented and maintained in GIT, plus there is also an [[piuparts/FAQ|FAQ]] available. |
| Line 57: | Line 24: |
| /%s -> /source/%s | === Documentation === |
| Line 59: | Line 26: |
| For PTS integration: one file with results for all source packages: /results-per-source.txt %s pass $MATCHINGLOG %s fail $MATCHINGLOG |
piuparts itself has a [[https://piuparts.debian.org/doc/README.txt|README]] and a [[https://manpages.debian.org/testing/piuparts/piuparts.1.en.html|manpage]] - read those before reading the [[piuparts/HowTos]]. |
| Line 64: | Line 28: |
| }}} | === Contributing === If you are interested in contributing, that's great! Here's a list to hopefully get you started: * join [[piuparts/Development|development]] efforts. Every little pull request helps. Check the BTS for plenty of wishlist bugs to tackle. * [[https://piuparts.debian.org/bug_howto.html|file bugs]] based on piuparts.d.o runs! * improve the documentation, both these wiki pages and what's in GIT has been growing over the years and it's showing. ---- ## This page is referenced from http://piuparts.debian.org CategoryPermalink CategoryPackaging |
What is 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: https://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 piuparts.debian.org. The piuparts.debian.org setup is documented and maintained in GIT, plus there is also an FAQ available.
Documentation
piuparts itself has a README and a manpage - read those before reading the piuparts/HowTos.
Contributing
If you are interested in contributing, that's great! Here's a list to hopefully get you started:
join development efforts. Every little pull request helps. Check the BTS for plenty of wishlist bugs to tackle.
file bugs based on piuparts.d.o runs!
- improve the documentation, both these wiki pages and what's in GIT has been growing over the years and it's showing.