|
Size: 4282
Comment: some more updates, some more links
|
Size: 1438
Comment: move to piuparts/piuparts.debian.org
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| [[TableOfContents(2)]] | <<TableOfContents(2)>> |
| Line 5: | Line 5: |
| = General info = | = Overview about piuparts = |
| Line 8: | Line 8: |
| Description: .deb package installation, upgrading, and removal testing tool | Description: .deb package installation, upgrading, and removal testing tool |
| Line 15: | Line 15: |
| . | . |
| Line 18: | Line 18: |
| Homepage: http://piuparts.debian.org | |
| Line 20: | Line 21: |
| piuparts runs on piuparts.cs.helsinki.fi aka piatti.debian.org and just like lintian should be run on every developer machine before uploading :) | 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 22: | Line 23: |
| piuparts logs are available at [http://piuparts.debian.org http://piuparts.debian.org] | 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 24: | Line 25: |
| #debian-qa is the irc-channel to coordinate work on irc, piuparts-devel is the project name on alioth. | = Advanced usage tips for piuparts = * This obviously implies you are familar with the manpage, README_1st and README_server :-D * [[piuparts/UseCases]] |
| Line 26: | Line 29: |
| == Machine info == * 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 == How to run piuparts on piatti == the piuparts stuff is partly in the piupartsm account (master end), 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 for more information see http://svn.debian.org/viewsvn/piuparts/piatti/README.txt If you want to help, please join #debian-qa and say so there. == Troubleshouting / maintainance == Sometimes the chroot tarballs in /home/piupartss/ need to be removed, currently there are sid.tar.gz and lenny.tar.gz /!\ we should just recreate them every week... = Developing piuparts = * alioth project * source code: svn.debian.org/piuparts[http://svn.debian.org/viewsvn/piuparts/] * mailing list: piuparts-devel@l.a.d.o[http://lists.alioth.debian.org/mailman/listinfo/piuparts-devel] * commit diff list: piuparts-commits@l.a.d.o[http://lists.alioth.debian.org/mailman/listinfo/piuparts-commits] * there was a ["SummerOfCode2007/PiupartsImprovements"] = Todo = == piuparts.debian.org related == see http://svn.debian.org/viewsvn/piuparts/piatti/README.txt == Codebase related == see http://svn.debian.org/viewsvn/piuparts/trunk/TODO == 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.) == Documentation == split this wiki page into subpages, so that the piuparts documentation can be mainained in the wiki, by exporting as docbook. update: use asciidoc suggested structure: * /piuparts - index page, just a table of contents * /piuparts/about - what is piuparts * /piuparts/devel - information how to participate in piuparts development * /piuparts/doc/software - piuparts documentation * /piuparts/doc/piatti - documenation about piuparts.cs.helsinki.fi * /piuparts/todo - todo list |
---- ## 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