apt/apt-pkg/orderlist.cc, branch 1.0.9.4 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.0.9.4 2014-03-13T12:58:45Z cleanup headers and especially #includes everywhere 2014-03-13T12:58:45Z David Kalnischkies david@kalnischkies.de 2014-03-05T21:11:25Z urn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f Beside being a bit cleaner it hopefully also resolves oddball problems I have with high levels of parallel jobs. Git-Dch: Ignore Reported-By: iwyu (include-what-you-use) Fix typos in documentation (codespell) 2014-02-22T17:34:33Z Michael Vogt mvo@debian.org 2014-02-22T17:34:33Z urn:sha1:1e3f4083db29bba600b9725e9456b0e140975c99 prefer Essentials over Removals in ordering score 2013-06-09T13:10:31Z David Kalnischkies kalnischkies@gmail.com 2013-05-21T15:10:21Z urn:sha1:978844db25deb7cd88b053bc2f4685caf2c61a75 Doing Removes early is good to have them out of the way, so they don't break 'Inst' or 'Conf' chains, but scoring them above Essentials means that we end up upgrading (many) less important packages before we handle big stuff like libc6 or debconf which not only fails if those less important packages have unannounced (strict) dependencies, but also leads to having these packages unconfigured for a long time triggering bugs in maintainer scripts for no good reason (#708831). So this commits sets the default value for remove scores to 100, which is below the one for essentials (200) and a lot lower than the previous default value (500). rewrite pkgOrderList::DepRemove to stop incorrect immediate setting 2013-06-09T13:09:55Z David Kalnischkies kalnischkies@gmail.com 2013-05-20T22:05:14Z urn:sha1:2de7157775551185beb3d7cb56e9f9f353e57ab4 Some squeeze → wheezy upgrades indicate that DepRemove runs amok in complicated setups as it wasn't correctly working with or-groups. Completely rewritten the check is now moving from or-group to or-group instead. The behavior should be the same as the code before, but (hopefully) with less bugs and more comments. Closes: 645713 various simple changes to fix cppcheck warnings 2013-03-10T11:24:13Z David Kalnischkies kalnischkies@gmail.com 2013-03-10T11:24:13Z urn:sha1:69c2ecbdc937e3c73fe67d3c9bce12a80d3ec7ec fix a bunch of cppcheck "(warning) Member variable '<#>' is not 2012-03-04T22:47:05Z David Kalnischkies kalnischkies@gmail.com 2012-03-04T22:47:05Z urn:sha1:dcaa1185506986142bccd990a5dca4c6ec1228cf initialized in the constructor." messages (no functional change) enable APT in unpack/configure ordering to handle loops as well 2011-09-14T18:22:31Z David Kalnischkies kalnischkies@gmail.com 2011-09-14T18:22:31Z urn:sha1:75a90b93257ea81d42331c03b56bd6589c62e065 as tight dependencies between immediate packages better enabling also the possibility to mark all packages as immediate (at least Closes: #353290, #540227, #559733, #621836, #639290) merge with debian/sid 2011-09-13T16:00:22Z David Kalnischkies kalnischkies@gmail.com 2011-09-13T16:00:22Z urn:sha1:afd7b358f94efddb83a2911ec1a21e7280074b1e merge with debian/experimental 2011-09-13T15:52:22Z David Kalnischkies kalnischkies@gmail.com 2011-09-13T15:52:22Z urn:sha1:74b220028595342028e3309002e4ec359af328f9 reorder includes: add <config.h> if needed and include it at first 2011-09-13T08:09:00Z David Kalnischkies kalnischkies@gmail.com 2011-09-13T08:09:00Z urn:sha1:ea54214002c09eeb4dd498d97a564471ec9993c5