summaryrefslogtreecommitdiff
path: root/test/integration/test-ubuntu-bug-835625-multiarch-lockstep-installed-first
AgeCommit message (Collapse)Author
2020-11-06Do not immediately configure m-a: same packages in lockstepJulian Andres Klode
In LP#835625, it was reported that apt did not unpack multi-arch packages in the correct order, and dpkg did not like that. The fix also made apt configure packages together, which is not strictly necessary. This turned out to cause issues now, because of dependencies on libc6:i386 that caused immediate configuration of that to not work. Work around the issue by not configuring multi-arch: same packages in lockstep if they have the immediate flag set. This will be the pseudo-essential set, and given how essential works, we mostly need the native arch to work correctly anyway. LP: #1871268 Regression-Of: 30426f4822516bdd26528aa2e6d8d69c1291c8d3
2015-12-19tests: support spaces in path and TMPDIRDavid Kalnischkies
This doesn't allow all tests to run cleanly, but it at least allows to write tests which could run successfully in such environments. Git-Dch: Ignore
2015-08-17Fix the test suite againJulian Andres Klode
Gbp-Dch: ignore
2012-04-19ignore the order used for the 'apt' package as long as it is valid either wayDavid Kalnischkies
2011-09-09M-A:same lockstep unpack should operate on installedDavid Kalnischkies
packages first (LP: #835625)