d2572c8878
If at some point in the future we have another transition as extensive as time64, then libgtk-3-0t64 could conceivably be replaced by some other package, which I have modelled here as libgtk-3-0xyz. If that happens, we need to avoid deletion of immmodules.cache, otherwise we will have another bug similar to #1065494. This test-case depends on several implementation details of dpkg-repack and libgtk-3-0t64, so it might need to be adjusted in the future. As a result, I have marked it as flaky, so that failures in the official autopkgtest environment will not be considered a release-critical bug that stalls migration and requires immediate intervention by maintainers.
12 lines
488 B
Plaintext
12 lines
488 B
Plaintext
Tests: build python3-gi
|
|
Depends: libgtk-3-dev, build-essential, xauth, xvfb, python3-gi, gir1.2-gtk-3.0, dbus-daemon
|
|
Restrictions: allow-stderr, superficial
|
|
|
|
Tests: installed-tests
|
|
Depends: adwaita-icon-theme-full, at-spi2-core, dbus-daemon, gnome-desktop-testing (>= 2018.1-1~), gtk-3-examples, librsvg2-common, xauth, xvfb
|
|
Restrictions: allow-stderr
|
|
|
|
Tests: 1065494-futureproofing
|
|
Depends: dpkg-dev, dpkg-repack, libgtk-3-0t64
|
|
Restrictions: allow-stderr breaks-testbed flaky needs-root
|