apt/test, branch 1.4_beta3Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.4_beta32017-01-02T13:28:05ZRun parsedepends_test for two different native archs2017-01-02T13:28:05ZJulian Andres Klodejak@debian.org2017-01-02T13:25:45Zurn:sha1:ae44d3935267b193e73071f3d110009d492021a6
Run the test for kfreebsd-i386 and amd64 and pass "amd64" as
an additional argument to the function. This tests that the
argument is used and thus ParseDepends returns the amd64
results even on a different architecture like i386.
allow warning generation for non-whitelisted options2016-12-31T17:24:12ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-31T17:24:12Zurn:sha1:ae73a2944a89e0d2406a2aab4a4c082e1e9da3f9
The idea is simple: Each¹ Find*( call starts with a call check if the
given option (with the requested type) exists in the whitelist. The
whitelist is specified via our configure-index file so that we have
a better chance at keeping it current. the whitelist is loaded via a
special (undocumented for now) configuration stanza and if none is
loaded the empty whitelist will make it so that no warnings are shown.
Much needs to be done still, but that is as good a time as any to take a
snapshot of the current state and release it into the wild given that it
found some bugs already and has no practical effect on users.
¹ not all in this iteration, but many
expand -f to --fix-broken in error messages2016-12-31T01:29:20ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-29T11:55:12Zurn:sha1:cfc11b2e1d8480727208b9d3e9577172de9a4038
Users end up believing that this is a --force mode as -f is common for
that, but apt doesn't have such a mode and --fix-broken is really not
about forcing something but actually trying to fix the breakage which
tends to be the result of a user forcing something on its system via
low-level forced dpkg calls.
Example: The "common" pattern of "dpkg -i ./foo.deb; apt install -f" is
nowadays far better dealt with via "apt install ./foo.deb".
And while at it the two places handing out this suggestion are changed
to use the same strings to avoid needless translation work in the future
and the suggestion uses 'apt' instead of 'apt-get' as this will be run
interactively by a user, so its a good opportunity to showcase what we
can do and will allow us to be more helpful to the user.
Closes: #709092
Thanks: Kristian Glass for initial patch!
allow default build-essentials to be overridden2016-12-31T01:29:20ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-29T11:41:23Zurn:sha1:abbe74b2b4690b9138da94d26a7e45ad80a3bf6c
The config list APT::Build-Essential gets a similar treatment to other
lists now by having the value of the option itself be an override for
the list allowing to disable build-essentials entirely as well as
adding/overriding as usual by now in other lists.
Reported-By: Johannes 'josch' Schauer on IRC
add --indep-only for build-dep command2016-12-31T01:29:20ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-29T11:12:01Zurn:sha1:0c646119dea438abb3ee8797994d016ba6834cd2
The implementation is quite different compared to --arch-only due to ABI
reasons but functionality wise they are similar and usually both
available for symmetry at least.
Closes: #845775
ensure generation of valid EDSP error stanzas2016-12-31T01:29:20ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-29T10:20:18Zurn:sha1:0161280405fe5aa256dc9df6a56106dd3a1a6f38
The crude way of preparing a message to be a multiline value failed at
generation valid deb822 in case the error message ended with a new line
like the resolving errors from apt do. apt itself can parse these, but
other tools like grep-dctrl choke on it, so be nice and print valid.
Reported-By: Johannes 'josch' Schauer on IRC
warn if clearsigned file has ignored content parts2016-12-31T01:29:19ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-16T18:50:48Zurn:sha1:6376dfb8dfb99b9d182c2fb13aa34b2ac89805e3
Clearsigned files like InRelease, .dsc, .changes and co can potentially
include unsigned or additional messages blocks ignored by gpg in
verification, but a potential source of trouble in our own parsing
attempts – and an unneeded risk as the usecases for the clearsigned
files we deal with do not reasonably include unsigned parts (like emails
or some such).
This commit changes the silent ignoring to warnings for now to get an
impression on how widespread unintended unsigned parts are, but
eventually we want to turn these into hard errors.
tests: cache the apt-key homedir used for Release signing2016-12-21T18:36:10ZDavid Kalnischkiesdavid@kalnischkies.de2016-12-18T16:42:17Zurn:sha1:4ce2f35248123ff2366c8c365ad6a94945578d66
Importing a new secret key into gpg(2) can be increadibly slow which
prolongs the test runs significantly – by caching the homedir we gain a
significant speedbonus as reimporting already present keys seems like a
far less costly operation.
Git-Dch: Ignore
let {dsc,tar,diff}-only implicitly enable download-only2016-12-16T12:50:00ZDavid Kalnischkiesdavid@kalnischkies.de2016-11-25T14:51:21Zurn:sha1:58ebb3017baf46e33a9bb2c1779d6daede27d108
That was the case already for tar-only and diff-only, but in a more
confusing way and without a message while dsc "worked" before resulting
in a dpkg-source error shortly after as tar/diff files aren't available…
optional write aptwebserver log to client specific files2016-11-24T23:15:13ZDavid Kalnischkiesdavid@kalnischkies.de2016-11-24T11:14:39Zurn:sha1:e1ae0531bfad0fce8590c26d1e38825df22d812a
The test test-handle-redirect-as-used-mirror-change serves multiple
clients at the same time, so the order of the output is undefined and
once in a while the two clients will intermix their lines causing the
grep we perform on it later to fail making our tests fail.
Solved by introducing client-specific logfiles which we all grep and
sort the result to have the results more stable.
Git-Dch: Ignore