[Piuparts-devel] Bug#784218: piuparts: Please document how to test upgrades of split packages

[Fabian Greffrath]

Am Mittwoch, den 06.05.2015, 13:18 +0200 schrieb Andreas Beckmann: 
> Would have been helpful to give these command lines ...

Sure, sorry.

$ grep piuparts ~/.bash_history 
[...]
sudo piuparts ../chocolate-doom_2.1.0-2_amd64.changes 
sudo piuparts ../chocolate-doom_2.1.0-2_amd64.deb ../chocolate-common_2.1.0-2_amd64.deb 
sudo piuparts -d unstable ../chocolate-doom_2.1.0-2_amd64.changes 
reportbug piuparts
[...]
sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs -a chocolate-doom
sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures -a chocolate-doom
sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends -a chocolate-doom
sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends -a -d sid chocolate-doom
sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends -a -d stable chocolate-doom
sudo piuparts --bindmount /tmp/repo --testdebs-repo /tmp/repo --distupgrade-to-testdebs --do-not-verify-signatures --install-recommends chocolate-doom_2.1.0-1_amd64.changes 

Please note that chocolate-doom_2.1.0-1 is the version currently in sid
and -2 is the version I prepared locally. In this version the package
has been split from 1 into 5 binary packages. If you need more
information about the package, please find it prepared here:

http://anonscm.debian.org/cgit/pkg-games/chocolate-doom.git

> --distupgrade-to-testdebs will be needed, perhaps with one or two
> -d <distro> options (even '-d sid -d sid' could work)

As you can see from the command lines I posted above, I already tried
various combinations of these parameters. The symptoms were always the
same: With the "-a" parameter, apt always preferred to install the local
package with the higher package revision. When passed the .changes file,
apt was always forced to install exactly this specific version by
passing the "=$version" suffix.

- Fabian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20150506/5518f11e/attachment.sig>