apt/test/integration/test-apt-update-rollback, branch 1.3_pre1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_pre12016-06-22T12:05:01Zadd [weak] tag to hash errors to indicate insufficiency2016-06-22T12:05:01ZDavid Kalnischkiesdavid@kalnischkies.de2016-06-18T13:15:27Zurn:sha1:d30036922c6963846db4ab633b13fb87c1b5b462
For "Hash Sum mismatch" that info doesn't make a whole lot of
difference, but for the new insufficient info message an indicator that
while this hashes are there and even match, they aren't enough from a
security standpoint.
tests: disable generation of Release.gpg by default2016-05-04T10:12:33ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-04T09:45:35Zurn:sha1:5a23c56d6852a27d45c2ae227b43060f7beac051
Most tests just need a signed repository and don't care if it signed by
an InRelease file or a Release.gpg file, so we can save some time by
just generating one of them by default.
Sounds like not much, but quickly adds up to a few seconds with the
amount of tests we have accumulated by now.
Git-Dch: Ignore
show more details for "Hash Sum mismatch" errors2016-04-25T13:35:52ZDavid Kalnischkiesdavid@kalnischkies.de2016-03-12T19:29:04Zurn:sha1:0340069cc4709a18ba117090763d9f263de999a9
Users tend to report these errors with just this error message… not very
actionable and hard to figure out if this is a temporary or 'permanent'
mirror-sync issue or even the occasional apt bug.
Showing the involved hashsums and modification times should help in
triaging these kind of bugs – and eventually we will have less of them
via by-hash.
The subheaders aren't marked for translation for now as they are
technical glibberish and probably easier to deal with if not translated.
After all, our iconic "Hash Sum mismatch" is translated at least.
These additions were proposed in #817240 by Peter Palfrader.
Report non-transient errors as errors, not as warnings2016-03-16T16:56:50ZJulian Andres Klodejak@debian.org2016-03-16T15:46:39Zurn:sha1:f695e76199a43b7f4d5816e20d18496b6448b833
This makes it easier to understand what really is an error
and what not.
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
new quiet level -qq for apt to hide progress output2015-11-04T17:04:03ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-25T11:35:00Zurn:sha1:2b0660b537581e9e65180e4cf1a94d763fd66847
-q is for logging and -qqq (old -qq) basically kills every output expect
errors, so there should be a way of declaring a middleground in which
the output of e.g. 'update' isn't as verbose, but still shows some
things. The test framework was actually making use of by accident as it
ignored the quiet level in output setup for apt before.
Eventually we should figure out some better quiet levels for all tools…
tests: try to support spaces in TMPDIR2015-09-14T13:22:19ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-14T00:26:13Zurn:sha1:63c7141275c8c5c0f6e60f5242785e50cabaf2a0
Not all tests work yet, most notable the cdrom tests, but those require
changes in libapt itself to have a proper fix and what we have fixed so
far is good enough progress for now.
Git-Dch: Ignore
Replace --force-yes by various options starting with --allow2015-08-14T10:38:18ZJulian Andres Klodejak@debian.org2015-08-14T09:49:45Zurn:sha1:b381a482eab0fc7b65b63cf0512ef1f97d775e34
This enables more fine grained control over such exceptions.
drop extra newline in 'Failed to fetch' and 'GPG error' message2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-08-09T17:01:49Zurn:sha1:0efb29eb36184bbe6de7b1013d1898796d94b171
I never understood why there is an extra newline in those messages, so
now is as good time as any to drop them. Lets see if someone complains
with a good reason to keep it…
show URI.Path in all acquire item descriptions2015-06-11T08:56:31ZDavid Kalnischkiesdavid@kalnischkies.de2015-06-11T08:56:31Zurn:sha1:1da3b7b8e15b642135b54684e70a0c271471f07a
It is a rather strange sight that index items use SiteOnly which strips
the Path, while e.g. deb files are downloaded with NoUserPassword which
does not. Important to note here is that for the file transport Path is
pretty important as there is no Host which would be displayed by Site,
which always resulted in "interesting" unspecific errors for "file:".
Adding a 'middle' ground between the two which does show the Path but
potentially modifies it (it strips a pending / at the end if existing)
solves this "file:" issue, syncs the output and in the end helps to
identify which file is meant exactly in progress output and co as a
single site can have multiple repositories in different paths.