[Piuparts-devel] Bug#802499: testing plugin packages during upgrades

[Andreas Beckmann]

On 2015-10-20 17:59, Daniel Pocock wrote:
> If a package and its plugins are packaged separately and if both
> packages are upgraded at the same time, problems can occur, e.g.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790951
> 
> Maybe piuparts can test for this scenario?
> 
> This would involve running the postinst scripts in different sequences.

In general, piuparts should be able to reproduce such scenarios (given
the right parameters).
But this specific problem would be a hard one since it involves starting
services, and that is generally forbidden via policy-rc.d (with the
exception of mysql/postgresql/... if --enable-database is given).

How would you describe such sets of "related" packages and which upgrade
scenarios would you like to test with them?


Similar to Ralf Treinen's co-installability tests in sid, I use piuparts
and dose to do similar things across distros.
Here two packages pkg1/testing and pkg2/sid are related
* if pkg1 != pkg2
* both contain at least one common file
* dose says they are coinstallable
And thereafter I have a script that tries get an installation with both
packages installed. That may succeed, or fail somewhere with a file
overwrite error or fail differently (in which case I try alternative
ways to get a working coinstalled setup).

Yes, some things are doable with piuparts (but not neccessarily within
piuparts, at least in the current master/slave setup).


Andreas