Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.11 2016-08-24T08:24:41Z 2016-08-24T08:24:41Z David Kalnischkies david@kalnischkies.de 2016-08-24T07:47:48Z urn:sha1:2e2865ae53a65c00dd55a892d5b48458f3110366 The bugreport shows a segfault caused by the code not doing the correct magical dance to remove an item from inside a queue in all cases. We could try hard to fix this, but it is actually better and also easier to perform these checks (which cause instant failure) earlier so that they haven't entered queue(s) yet, which in return makes cleanup trivial. The result is that we actually end up failing "too early" as if we wouldn't be careful download errors would be logged before that process was even started. Not a problem for the acquire system, but likely to confuse users and programs alike if they see the download process producing errors before apt was technically allowed to do an acquire (it didn't, so no violation, but it looks like it to the untrained eye). Closes: 835195 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-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-09-26T22:10:05Z David Kalnischkies david@kalnischkies.de 2014-08-17T10:30:21Z urn:sha1:2a884c612b10b27f4be2cc6dd689bfe448d9361a Previously, we had a start and a done of the calculation printed by higher-level code, but this got intermixed by progress reporting from an external solver or the output of autoremove code… The higherlevel code is now only responsible for instantiating a progress object of its choosing (if it wants progress after all) and the rest will be handled by the upgrade code. Either it is used to show the progress of the external solver or the internal solver will give some hints about its overall progress. The later isn't really a proper progress as it will jump forward after each substep, but that is at least a bit better than before without any progress indication. Fixes also the 'strange' non-display of this progress line in -q=1, while all others are shown, which is reflected by all testcase changes. 2011-02-15T15:04:46Z Michael Vogt mvo@debian.org 2011-02-15T15:04:46Z urn:sha1:adee3bae782f5b7d83819bf92ab419663ef4ee64 2010-11-29T20:43:07Z David Kalnischkies kalnischkies@gmail.com 2010-11-29T20:43:07Z urn:sha1:c427b1e218e61bd1aacbddf9013e58b8aa445a7c - mark all installed packages first without auto installation in a dist-upgrade to prefer upgrading packages instead of installing new packages in versioned or-groups (Closes: #605394)