apt/test/integration/framework, branch 1.1.10Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.102015-12-19T22:04:34Ztests: 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 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.
test framework: Unset no_proxy as well2015-12-14T12:33:55ZJulian Andres Klodejak@debian.org2015-12-14T12:33:55Zurn:sha1:59f57473ab85d3fb3354d086db2df2466c1c3896
This caused test-bug-717891-abolute-uris-for-proxies to fail
Gbp-Dch: ignore
test framework: Unset http proxy variables in setupenvironment2015-12-14T12:27:34ZJulian Andres Klodejak@debian.org2015-12-14T12:27:00Zurn:sha1:1ba0302352b320108b3ca23130ceca1d46f0a999
This breaks a lot of test cases
Gbp-Dch: ignore
test framework: Correctly generate new paths in noopchroot2015-12-14T12:14:22ZJulian Andres Klodejak@debian.org2015-12-14T12:12:37Zurn:sha1:d27daedb6a0bf672508072100f20233d08ccf0e0
The allocated buffer was one byte too small. Allocate a buffer
of PATH_MAX instead and use snprintf(), as suggested by Martin
Pitt.
non-existing directories don't need to be cleaned2015-12-14T02:21:20ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-14T02:21:20Zurn:sha1:dffc17ba835b6bf782fe553d338b6a921c6de7bf
Trying to clean up directories which do not exist seems rather silly if
you think about it, so let apt think about it and stop it.
Depends a bit on the caller if this is fixing anything for them as they
might try to acquire a lock or doing other clever things as apt does.
Closes: 807477
show a more descriptive error for weak Release files2015-12-14T01:26:23ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-14T01:18:25Zurn:sha1:bd4a8f51649ee37291c6e07310104a94f4f5fbed
If we can't work with the hashes we parsed from the Release file we
display now an error message if the Release file includes only weak
hashes instead of downloading the indexes and failing to verify them
with "Hash Sum mismatch" even through the hashes didn't mismatch (they
were just weak).
If for some (unlikely) reason we have got weak hashes only for
individual targets we will show a warning to this effect (again, befor
downloading and failing the index itself).
Closes: 806459
replace "which" with "command -v" for portability2015-12-06T13:03:35ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-06T13:03:35Zurn:sha1:e75e5879c0e8d232a2e8f045685beeb8c965aba4
which is a debian specific tool packaged in debianutils (essential)
while command is a shell builtin defined by POSIX.
Closes: 807144
Thanks: Mingye Wang for the suggestion.