Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.2.0 2017-01-18T23:57:38Z 2017-01-18T23:57:38Z David Kalnischkies david@kalnischkies.de 2017-01-18T10:31:13Z urn:sha1:33f982b90a4f77be18cb82daf8c79e9c5513761c Unlikely that anyone is actually running into this, but if we asked to not generate a cache and avoid it in the first step we shouldn't create one implicitly anyway by displaying the statistics. 2015-12-19T22:04:34Z David Kalnischkies david@kalnischkies.de 2015-12-15T16:20:26Z urn: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 2015-11-04T17:04:03Z David Kalnischkies david@kalnischkies.de 2015-10-25T11:35:00Z urn: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… 2015-08-10T15:25:26Z David Kalnischkies david@kalnischkies.de 2015-06-23T13:16:08Z urn:sha1:5ad0096a4e19e191b59634e8a8817995ec4045ad indexRecords was used to parse the Release file – mostly the hashes – while metaIndex deals with downloading the Release file, storing all indexes coming from this release and … parsing the Release file, but this time mostly for the other fields. That wasn't a problem in metaIndex as this was done in the type specific subclass, but indexRecords while allowing to override the parsing method did expect by default a specific format. APT isn't really supporting different types at the moment, but this is a violation of the abstraction we have everywhere else and, which is the actual reason for this merge: Options e.g. coming from the sources.list come to metaIndex naturally, which needs to wrap them up and bring them into indexRecords, so the acquire system is told about it as they don't get to see the metaIndex, but they don't really belong in indexRecords as this is just for storing data loaded from the Release file… the result is a complete mess. I am not saying it is a lot prettier after the merge, but at least adding new options is now slightly easier and there is just one place responsible for parsing the Release file. That can't hurt. 2015-03-16T17:01:54Z David Kalnischkies david@kalnischkies.de 2015-03-09T23:59:44Z urn: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 2014-11-18T01:41:20Z David Kalnischkies david@kalnischkies.de 2014-11-09T20:38:53Z urn:sha1:081c9d442a6d39fb9bc419fe3ce697cc791cb844 Usually they don't provide a lot in terms of what they test, but they help in covering many lines from strictly anecdotal commands (stats, moo) and error messages, so that stuff which really needs to be tested, but isn't is better visible in coverage reports. Git-Dch: Ignore 2014-10-20T08:37:46Z David Kalnischkies david@kalnischkies.de 2014-10-19T12:14:37Z urn:sha1:1df24acfdb8ba1cd8bbbaa166f170dda480ce41e These functions check the exit code of the command, but for apt commands we can go further and require an error message for non-zero exits and none for zero exits. Git-Dch: Ignore 2014-05-22T06:39:44Z Michael Vogt mvo@debian.org 2014-04-22T14:07:32Z urn:sha1:8f418981337503ff7abedd872f788b51bcdbc886 Closes: 748389