apt/test/integration, branch 1.1.10Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.102015-12-29T02:29:29ZFix test case that was broken by switch of hash function2015-12-29T02:29:29ZJulian Andres Klodejak@debian.org2015-12-29T02:29:29Zurn:sha1:202555ac668291065d04c339f36dd4c129945db9
This test relies on the ordering of the hash function.
allow repositories to forbid arch:all for specific index targets2015-12-27T16:04:33ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-27T16:04:33Zurn:sha1:a628ca5256b4a2f3ae300697b17adf150b6e17b0
Debian has a Packages file for arch:all already, but the arch:any files
contain arch:all packages as well, so downloading it would be a total
waste of resources. Getting this solved is on the list of things to do,
but it is also the hardest part – for index targets like Contents the
situation is much easier and less server/client implementations are
involved so we might not want to stall them.
A repository can now declare via:
No-Support-for-Architecture-all: Packages
that even if an arch:all Packages exists, it shouldn't be downloaded, so
that support for Contents files can be added now.
See also 1dd20368486820efb6ef4476ad739e967174bec4 for the implementation
of downloading arch:all index targets, which this is limiting.
The field uses the name of the target from the apt configuration for
simplicity and is negative by design as this field is intended to be
supported/needed only for a "short" time (one or two Debian releases).
While this commit theoretically supports any target, its expected to
only see "Packages" as a value in reality.
ensure we got a lock in clean operation2015-12-23T16:48:16ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-23T16:48:16Zurn:sha1:8d968cc2d1e11da81f3bab878c1a413a97ca27ed
We try to acquired the locks, but we didn't stop if we failed to get it…
Closes: 808561
tests: support gpg2 properly in all testcases2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-18T12:17:11Zurn:sha1:785cb6fc843f4751ff9c57dcdf375ad061e83f36
The output changes slightly between different versions, which we already
dealt with in the main testcase for apt-key, but there are two more
which do not test both versions explicitly and so still had gpg1 output
to check against as this is the default at the moment.
Git-Dch: Ignore
avoid evaluating shell in paths used in apt-key2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-17T16:41:11Zurn:sha1:bc8f83a5afd858206efe518c31bbb1ac948a39a3
apt-key creates internally a script (since ~1.1) which it will call to
avoid dealing with an array of different options in the code itself, but
while writing this script it wraps the values in "", which will cause
the shell to evaluate its content upon execution.
To make 'use' of this either set a absolute gpg command or TMPDIR to
something as interesting as:
"/tmp/This is fü\$\$ing cràzy, \$(man man | head -n1 | cut -d' ' -f1)\$!"
If such paths can be encountered in reality is a different question…
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
test-apt-download-progress: Run the https test multiple times2015-12-14T15:43:27ZJulian Andres Klodejak@debian.org2015-12-14T15:43:27Zurn:sha1:56873870ce6c118b3ce58f7d7cc9b5762f2be113
This filters out errors due to timing issues. Early exits if
enough pulses occured.
pkgcache: Make hash arch-independent using fixed size integer2015-12-14T15:16:56ZJulian Andres Klodejak@debian.org2015-12-14T15:15:36Zurn:sha1:6755060951828412e19e58afe5361f9ad06e5deb
This helps writing test cases. Also adapt the test case that
expected 64-bit.
Nothing changes performance wise, the distribution of the hash
values remains intact.
tagfile: Hardcode error message for out of range integer values2015-12-14T12:58:46ZJulian Andres Klodejak@debian.org2015-12-14T12:58:46Zurn:sha1:137e8ad4b6ce28b1a1355d5a125d09670388c2b7
This makes the test suite work on 32 bit-long platforms.
Gbp-Dch: ignore
test framework: More noopchroot fixes2015-12-14T12:40:39ZJulian Andres Klodejak@debian.org2015-12-14T12:39:52Zurn:sha1:950733c947acd50afe498e900954d911454c57e7
Use asprintf() so we have easy error detection and do not depend
on PATH_MAX.
Do not add another separator to the generated path, in both cases
the path inside the chroot is guaranteed to have a leading /
already.
Also pass -Wall to gcc.