[Piuparts-devel] Bug#700849: Bug#700849: Bug#700849: add more advanced usage tips to README

Andreas Beckmann anbe at debian.org
Sun Feb 24 16:21:47 UTC 2013

On 2013-02-24 17:02, Holger Levsen wrote:
> Hi Andreas,
> On Donnerstag, 21. Februar 2013, Andreas Beckmann wrote:
>> Here is the script I used recently to do install and upgrade tests
>> for packages I NMUed (targetting wheezy via sid, or t-p-u, or s-p-u)
>> But I always copied it, adjusted LOCAL and logprefix and set FROM/VIA/TO
>> as appropriate ... (setting only FROM or TO switches from distupgrade to
>> install+purge and install-upgrade-purge test)
> do you think this could be made more generic and put into 
> /usr/share/doc/piuparts/examples ?

So, what would an average package developer find useful to test his
packages with piuparts?

Probably he would like to call

  piuparts-do-something my.changes

and that should test

install-purge sid
install-upgrade-purge sid
distupgrade testing unstable+TESTDEBS
distupgrade stable testing+TESTDEBS
distupgrade stable testing sid+TESTDEBS

for each package in my.changes

That should probably produce a bunch of logfiles (how should we name
them?) and finally a summary listing all tests as PASS/FAIL

For preparing updates for PU a few more steps would be needed ...


More information about the Piuparts-devel mailing list