|
Size: 1895
Comment: CategoryPackaging
|
Size: 1912
Comment: manpage link was 404.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 26: | Line 26: |
| 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]]. | piuparts itself has a [[https://piuparts.debian.org/doc/README.html|README]] and a [[https://manpages.debian.org/testing/piuparts/piuparts.1.en.html|manpage]] - read those before reading the [[piuparts/HowTos]]. |
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.