[Piuparts-devel] Bug#679780: ia32-libs: please document how to perform automated package install and upgrade tests that involve ia32-libs
debian at abeckmann.de
Sun Jul 1 13:52:20 UTC 2012
please provide detailed instructions how to perform piuparts tests on
packages that depend on (or are) ia32-libs. These tests are done
fully automatic with DEBIAN_FRONTEND=noninteractive.
Ideally provide custom scripts that can be added to /etc/piuparts/scripts/
There are primarily two tests to be considered:
* installation in a minimal sid (and later wheezy, too) chroot
* dist-upgrade tests from squeeze to wheezy or to sid
Piuparts supports running custom scripts at certain phases of the test.
For the installation test, it's probably a pre_install script that needs
to be added that runs dpkg --add-architecture and apt-get update if and
only if this is neccessary, i.e. I don't want to always enable a foreign
The environment variables PIUPARTS_OBJECTS, PIUPARTS_DISTRIBUTION,
PIUPARTS_TEST, PIUPARTS_PHASE should provide the information needed to
decide the operations.
For the dist-upgrade test the following will be done in the chroot:
* replace sources.list to point ot the next distribution
* run pre_distupgrade scripts (above variables + PIUPARTS_DISTRIBUTION_NEXT)
* apt-get dist-upgrade
* run post_distupgrade scripts (above variables + PIUPARTS_DISTRIBUTION_PREV)
The pre-distupgrade script can probably check for certain packages being
installed currently that require enabling i386 as a foreign architecture
to perform the upgrade.
Please see the piuparts documentation for details:
I'm asking the ia32-libs maintainers since I assume they will write that
respective chapter for the release notes, so these scripts should
reflect what's being written into the release notes.
And you probably want to know whether the ia32-libs upgrade path is
smooth if the instructions are followed.
Please reassign this bug to piuparts after adding sufficient
More information about the Piuparts-devel