apt/test/integration/test-sourceslist-trusted-options, branch 2.7.11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.112016-12-16T12:50:00Zlet {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…
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
review of new/changed translatable program strings2015-11-21T17:04:29ZJustin B Ryejustin.byam.rye@gmail.com2015-11-21T16:50:06Zurn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910
Reference mail:
https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
rework errors and warnings around insecure repositories2015-11-04T17:04:01ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-13T09:37:39Zurn:sha1:f18f2338a17d3037ac0d6f81a7f1a37df6eaca01
Insecure (aka unsigned) repositories are bad, period. We want to get
right of them finally and as a first step we are printing scary
warnings. This is already done, this commit just changes the messages to
be more consistent and prevents them from being displayed if
authenticity is guaranteed some other way (as indicated with
trusted=yes).
The idea is to first print the pure fact like "repository isn't signed"
as a warning (and later as an error), while giving an explaination in a
immediately following notice (which is displayed only in quiet level 0:
so in interactive use, not in scripts and alike).
Closes: 796549
detect and error out on conflicting Trusted settings2015-08-10T15:25:26ZDavid Kalnischkiesdavid@kalnischkies.de2015-06-22T10:34:11Zurn:sha1:268ffcebb9ae4278b1e3c3f89f8167f229164dbd
A specific trust state can be enforced via a sources.list option, but it
effects all entries handled by the same Release file, not just the entry
it was given on so we enforce acknowledgement of this by requiring the
same value to be (not) set on all such entries.
test exitcode as well as string equality2015-03-16T17:01:54ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T23:59:44Zurn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e
We use test{success,failure} now all over the place in the framework, so
its only consequencial to do this in the situations in which we test for
a specific output as well.
Git-Dch: Ignore
chown finished partial files earlier2014-10-22T23:28:05ZDavid Kalnischkiesdavid@kalnischkies.de2014-10-22T23:28:05Zurn:sha1:03aa08472dcd689572a46ce6efdb1dccf6136334
partial files are chowned by the Item baseclass to let the methods work
with them. Now, this baseclass is also responsible for chowning the
files back to root instead of having various deeper levels do this.
The consequence is that all overloaded Failed() methods now call the
Item::Failed base as their first step. The same is done for Done().
The effect is that even in partial files usually don't belong to
_apt anymore, helping sneakernets and reducing possibilities of a bad
method modifying files not belonging to them.
The change is supported by the framework not only supporting being run
as root, but with proper permission management, too, so that privilege
dropping can be tested with them.
testcases: do not allow warnings in testsuccess2014-10-20T08:37:46ZDavid Kalnischkiesdavid@kalnischkies.de2014-10-20T08:23:41Zurn:sha1:4fa34122cbe347d21b3a162ff2fa75dd2e73c3a8
Adds a new testwarning which tests for zero exit and the presents of a
warning in the output, failing if either is not the case or if an error
is found, too. This allows us to change testsuccess to accept only
totally successful executions (= without warnings) which should help
finding regressions.
Git-Dch: Ignore
testcases runable as root2014-10-15T01:47:50ZDavid Kalnischkiesdavid@kalnischkies.de2014-10-15T01:47:50Zurn:sha1:68ba0b7f4e1c03edfb6f621e7e7314ea610af96b
Running the testcases is usually not a good idea, but it can be handy to
check if the privilege dropping works.
Git-Dch: Ignore
fix compile and tests error2014-10-13T11:01:15ZDavid Kalnischkiesdavid@kalnischkies.de2014-10-13T07:54:21Zurn:sha1:9d653a6de2ca952247cc4e628256259d225570a6
I am pretty sure I did that before committing broken stuff…
Git-Dch: Ignore