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

[Daniel Pocock]

On 20/10/15 19:45, Andreas Beckmann wrote:
> 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?
> 


a) sets of related packages:
    package foo : a package with an init script
    package foo-plugin:
       - has a dependency on foo
       - possibly has plugin or module or extension in the name
       - postinst or other script restarts foo daemon

b) scenarios to test would be something like:

     upgrade runs foo/postinst before foo-plugin/postinst

     upgrade runs foo-plugin/postinst before foo/postinst