<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-ubuntu-bug-835625-multiarch-lockstep-installed-first, branch master</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=master</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2020-11-06T09:51:06Z</updated>
<entry>
<title>Do not immediately configure m-a: same packages in lockstep</title>
<updated>2020-11-06T09:51:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2020-10-08T09:50:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2b13473a9b9947f55a0871d146e4fee456b0af60'/>
<id>urn:sha1:2b13473a9b9947f55a0871d146e4fee456b0af60</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>tests: support spaces in path and TMPDIR</title>
<updated>2015-12-19T22:04:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-12-15T16:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2'/>
<id>urn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Fix the test suite again</title>
<updated>2015-08-17T16:37:18Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2015-08-17T16:37:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e7ebb41440cbe298b07c7fb7c6b20a64a17200f0'/>
<id>urn:sha1:e7ebb41440cbe298b07c7fb7c6b20a64a17200f0</id>
<content type='text'>
Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>ignore the order used for the 'apt' package as long as it is valid either way</title>
<updated>2012-04-19T08:29:02Z</updated>
<author>
<name>David Kalnischkies</name>
<email>kalnischkies@gmail.com</email>
</author>
<published>2012-04-19T08:29:02Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=04d24dbdcc2eabf616b26878084d3b8790e30086'/>
<id>urn:sha1:04d24dbdcc2eabf616b26878084d3b8790e30086</id>
<content type='text'>
</content>
</entry>
<entry>
<title>M-A:same lockstep unpack should operate on installed</title>
<updated>2011-09-09T10:35:22Z</updated>
<author>
<name>David Kalnischkies</name>
<email>kalnischkies@gmail.com</email>
</author>
<published>2011-09-09T10:35:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=30426f4822516bdd26528aa2e6d8d69c1291c8d3'/>
<id>urn:sha1:30426f4822516bdd26528aa2e6d8d69c1291c8d3</id>
<content type='text'>
packages first (LP: #835625)</content>
</entry>
</feed>
