|
Size: 3890
Comment: remove stuff which is already in trunk/TODO
|
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 3: | Line 3: |
| <<TableOfContents(2)>> = General info = |
=== What is piuparts? === |
| Line 8: | Line 6: |
| Description: .deb package installation, upgrading, and removal testing tool | Description: .deb package installation, upgrading, and removal testing tool |
| Line 15: | Line 13: |
| . | . |
| Line 18: | Line 16: |
| Homepage: https://piuparts.debian.org | |
| Line 20: | Line 19: |
| piuparts is being run constantly on piuparts.cs.helsinki.fi aka piatti.debian.org - and/but just like lintian it also should be run on every developer machine before uploading :) | === piuparts.debian.org === |
| Line 22: | Line 21: |
| piuparts results are available at [[http://piuparts.debian.org|http://piuparts.debian.org]] | 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 24: | Line 24: |
| == Machine info == | === Documentation === |
| Line 26: | Line 26: |
| * piuparts.cs.helsinki.fi aka [[http://db.debian.org/machines.cgi?host=piatti|piatti.debian.org]] * hosted at [[http://cs.helsinki.fi/index.en.html|Department of Computer Science, University of Helsinki]] * donated by [[http://hp.com/go/debian/|HP]] * dual AMD Opteron(tm) Processor 275, 2.2 Ghz * 8GB RAM * 300 GB physical volume for data |
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 33: | Line 28: |
| == How piuparts is setup on piatti == | === Contributing === |
| Line 35: | Line 30: |
| Running piuparts is the easy, automated part and is supervised by Luk and Holger, who can su into the piupartss (slave) user. piuparts-slave.py is run in a shared screen session and seldom needs interaction. The piupartss user needs to be able to run piuparts and thus can use sudo without restrictions. |
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. |
| Line 38: | Line 35: |
| The slave automatically starts the master, to reserve packages to process and to pass logfiles to the master. Ideally all members of the Debian-QA group can su to the piupartsm user and process the logfiles - currently it's again only Luk and Holger. piupartsm has no special privileges. If you want to help, please join #debian-qa and say so there. Every hour piuparts-reports.py is run as piupartsm by cron to generate the html output of the logs. For more information see http://svn.debian.org/viewsvn/piuparts/piatti/README.txt = Developing piuparts = * alioth project * source code: [[http://svn.debian.org/viewsvn/piuparts/|svn.debian.org/piuparts]] * mailing list: [[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]] * codebase related todo: http://svn.debian.org/viewsvn/piuparts/trunk/TODO * piuparts.debian.org related todo: http://svn.debian.org/viewsvn/piuparts/piatti/README.txt * there was a [[SummerOfCode2007/PiupartsImprovements]] == 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: {{{ %s = source package name %v = source package version %p = piuparts version /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 similar for /binary-$ARCH/ /%s -> /source/%s For PTS integration: one file with results for all source packages: /results-per-source.txt %s pass $MATCHINGLOG %s fail $MATCHINGLOG }}} /!\ Problem: PTS is source package centered, piuparts binary package. {{{ For Ubuntu development weather report (similar to PTS): a file with the following: Pass: %d Fail: %d }}} (See https://blueprints.launchpad.net/ubuntu/+spec/developer-weather-report for the Ubuntu developer weather report.) |
---- ## 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.