apt/test/integration/test-dpkg-assert-multi-arch, branch 2.2.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.2.12016-08-10T21:51:35Zdisable explicit configuration of all packages at the end2016-08-10T21:51:35ZDavid Kalnischkiesdavid@kalnischkies.de2016-07-28T07:13:24Zurn:sha1:28557f94578602f9ce0011501a2259bd98ab0688
With b4450f1dd6bca537e60406b2383ab154a3e1485f we dropped what we
calculated here later on and now that we don't need it in the meantime
either we can just skip the busy work by default and expect dpkg to do
the right thing dropping also our little "last explicit configures"
removal trick introduced in b4450f1dd6bca537e60406b2383ab154a3e1485f.
This enables the last of a bunch of previously experimental options,
some of them existing still, but are very special and hence not really
worth documenting anymore (especially as it would need to be rewritten
now entirely) which is why the documentation is nearly completely
dropped.
The order of configuration stanzas in the simulation code changes
slightly as it isn't concerning itself with finding the 'right' order,
but any order is valid anyhow as long as the entire set happens in the
same call.
support dpkg debug mode in APT::StateChanges2016-07-22T14:05:09ZDavid Kalnischkiesdavid@kalnischkies.de2016-07-03T21:09:04Zurn:sha1:27f38567fe327ecaf7fb361c3cca6ee29e6300c9
Gbp-Dch: Ignore
don't explicitly configure the last round of packages2016-06-08T15:31:45ZDavid Kalnischkiesdavid@kalnischkies.de2016-06-08T15:31:45Zurn:sha1:b4450f1dd6bca537e60406b2383ab154a3e1485f
We end our operation by calling "dpkg --configure -a", so instead of
running a (big) configure run with all packages mentioned explicitly
before this, we simply skip them and let them be handled by this call
implicitly.
There isn't really an observeable gain to be had here from a speed
point, but it helps in avoiding an (uncommon) problem of having a too
long commandline passed to dpkg, which we would split up (probably
incorrectly).
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
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
properly handle (currently unused) dpkg pass-through2014-07-07T19:52:40ZDavid Kalnischkiesdavid@kalnischkies.de2014-07-07T18:45:28Zurn:sha1:eb191ca3584816533e82cd6b8cd1f133ae28149a
Git-Dch: ignore
use exit instead of incorrect return in test wrapper2014-07-07T19:52:31ZMichele Orrùmaker@tumbolandia.net2014-07-07T18:43:45Zurn:sha1:4f445ff78220568e0fcfa373ba1b06e0ad13e63d
bash as sh doesn't like it, too.
Git-Dch: Ignore
* apt-pkg/cacheiterators.h:2012-01-19T17:42:57ZDavid Kalnischkieskalnischkies@gmail.com2012-01-19T17:42:57Zurn:sha1:2a2a7ef4dfa9d8fb8118c2e318555438098cdf34
- return the correct version arch for all+foreign, too
The flag is interpreted at a few other places in different styles so
this commit ensures that the flag check is consistent everywhere
(checking for Same in flag style is a bit too much as it isn't used
in combination with others anyway, but who knows and just for
consistency)if multi-arch is detected ensure that pkg:all is reported as pkg:all2012-01-19T12:12:14ZDavid Kalnischkieskalnischkies@gmail.com2012-01-19T12:12:14Zurn:sha1:3a5ec3053c00ff5db058f1ddd99bf23591b9a181
Versions with arch:all are added to the package with the native arch,
so we can't rely on Pkg.Arch() for the architecture* apt-pkg/deb/dpkgpm.cc:2012-01-19T11:40:38ZDavid Kalnischkieskalnischkies@gmail.com2012-01-19T11:40:38Zurn:sha1:67b5d3dc34e88e092c8e5f05efc82370a873c80f
- redirect out/input of dpkg --assert-multi-arch to /dev/null* apt-pkg/deb/dpkgpm.cc:2012-01-13T16:30:17ZDavid Kalnischkieskalnischkies@gmail.com2012-01-13T16:30:17Zurn:sha1:86fc2ca8909eb686e2ad751acb0f0eaf706d9d5e
- check if dpkg supports multiarch with --assert-multi-arch
and if it does be always explicit about the architecture