|
Size: 2458
Comment: restructure
|
Size: 1877
Comment: broken link - now it's just a README
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| <<TableOfContents(2)>> | === What is piuparts? === |
| Line 5: | Line 5: |
| = 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: https://piuparts.debian.org }}} |
| Line 7: | Line 19: |
| {{{ Description: .deb package installation, upgrading, and removal testing tool }}} | === piuparts.debian.org === |
| Line 9: | Line 21: |
| 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]]. | 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 11: | Line 24: |
| piuparts itself has a [[http://piuparts.debian.org/doc/README_1st.html|README_1st]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|piuparts manpage]], for the piuparts.debian.org setup there is also an [[http://wiki.debian.org/piuparts/FAQ|FAQ]] available. Below is an overview of information not covered elsewhere. | === Documentation === |
| Line 13: | Line 26: |
| = Useful links for piuparts development = | piuparts itself has a [[https://piuparts.debian.org/doc/README.html|README]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|manpage]] - read those before reading the [[piuparts/HowTos]]. |
| Line 15: | Line 28: |
| * alioth project: [[https://alioth.debian.org/projects/piuparts/]] * source code: * Browse it: [[https://alioth.debian.org/scm/browser.php?group_id=30965]] * Get it: `git clone git://anonscm.debian.org/piuparts/piuparts.git` * mailing lists: * development: [[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]] * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=TODO;hb=develop|TODO]] |
=== Contributing === |
| Line 24: | Line 30: |
| = More ressources for using piuparts = * [[http://piuparts.debian.org/doc/README_server.html|README_server]] * piuparts.conf.anbe * piuparts.conf.goldwasser * [[piuparts/UseCases]] = More ressources about piuparts.debian.org = * [[http://anonscm.debian.org/gitweb/?p=piuparts/piuparts.git;a=blob;f=READNE_pejecevic.txt;hb=HEAD|README_pejecevic.txt]] - information how the setup has been made together with [[Teams/DSA|DSA]]. * piuparts.d.o reports list: [[http://lists.alioth.debian.org/mailman/listinfo/piuparts-reports|piuparts-reports@l.a.d.o]] = Old development efforts = * there was a [[SummerOfCode2007/PiupartsImprovements]] * [[http://www.ohloh.net/p/9038|code analysis]] and more on ohloh (needs update) * Developing piuparts, the rewrite of version 2 * stalled at planning stage * in bzr: bzr get http://code.liw.fi/piuparts2/bzr/trunk/ (may move to bzr.debian.org later) * From the BoF at Debconf9 * new output format: http://lists.debian.org/debian-devel/2009/07/msg00662.html * piuparts should not fail just because dependencies fail |
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. |
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.