Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.5 2022-09-28T14:32:44Z 2022-09-28T14:32:44Z Julian Andres Klode julian.klode@canonical.com 2022-09-28T14:28:36Z urn:sha1:5f5a8deedffac3cdeeb2f178d910d3759d366e8e By marking them at the end, we might make other decisions that depend on the new phased updates, confusing the solver. Run the marking at the start too. The EDSP test file from Jeremy was modified to include Machine-ID and Phased-Update-Percentage fields and then filtered to mostly exclude packages irrelevant to the test case by running grep-dctrl \( -FRequest "EDSP 0.5" -o -FInstalled yes \ -oFPhased-Update-Percentage 10 \) \ -a --not -FArchitecture i386 LP: #1990586 2022-06-28T12:25:18Z Julian Andres Klode julian.klode@canonical.com 2022-06-24T14:09:24Z urn:sha1:db131677bee45c86031d37d7b451e6ece692efb2 This is a lot closer to the original implementation in update-manager, but still has a couple of differences that might cause bugs: - When checking whether a version is a security update, we only check versions in between and not any later version. This happens mostly because we do not know the suite, so we just check if there is any version between the installed version and our target that is a security update - We only keep already installed packages, as we run before the resolver. update-manager first runs the resolver, and then marks for keep all packages that were upgraded or newly installed that are phasing (afaict). This approach has a significant caveat that if you have version 1 installed from a release pocket, version 2 is in security, and version 3 is phasing in updates, that it installs version 3 rather than 2 from security as the policy based implementation does. It also means that apt install does not respect phasing and would always install version 3 in such a scenario. LP: #1979244 2019-02-26T15:31:20Z Julian Andres Klode julian.klode@canonical.com 2019-02-26T10:33:11Z urn:sha1:eeecbe521fdad69a924992f505d0a32b53800cfc 2017-07-12T11:57:51Z Julian Andres Klode jak@debian.org 2017-07-12T11:40:41Z urn:sha1:87274d0f22e1dfd99b2e5200e2fe75c1b804eac3 This makes it easier to see which headers includes what. The changes were done by running git grep -l '#\s*include' \ | grep -E '.(cc|h)$' \ | xargs sed -i -E 's/(^\s*)#(\s*)include/\1#\2 include/' To modify all include lines by adding a space, and then running ./git-clang-format.sh. 2017-07-12T11:56:05Z Julian Andres Klode jak@debian.org 2017-07-12T11:42:18Z urn:sha1:c46f94aa48a9707668c46118b3eec77ff318b78c Including cacheiterators.h before pkgcache.h fails because pkgcache.h depends on cacheiterators.h. 2017-01-19T14:59:38Z David Kalnischkies david@kalnischkies.de 2017-01-19T14:14:19Z urn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee Most of them in (old) code comments. The two instances of user visible string changes the po files of the manpages are fixed up as well. Gbp-Dch: Ignore Reported-By: spellintian 2016-06-08T11:09:42Z David Kalnischkies david@kalnischkies.de 2016-06-08T09:34:53Z urn:sha1:3a487cc03dec3488d0fa3008d04747bb1b4b0baf Create and log the EDSP(like) request even if we use the internal resolver. 2016-06-08T11:07:21Z David Kalnischkies david@kalnischkies.de 2016-06-08T08:56:14Z urn:sha1:4dc619c0435d44a6a03cfda357654d3d76833b68 It wasn't noticeable before, but now with the (optional) logging it can be observed that we decide in the internal path two times if an internal or external solver should be used (and hence with logging, it is attempted twice), so if we are in the internal path call the internal resolver directly, which means those internal methods need to be public – but we can hide them based on the symbol at least. 2016-05-20T12:18:36Z David Kalnischkies david@kalnischkies.de 2016-05-06T12:21:02Z urn:sha1:43c71fad3a51d841132ba15a7a5930e1ee4126ed This allows to differentiate properly between 'apt-get upgrade', 'apt upgrade' and 'apt full-upgrade'. 2016-04-13T19:33:32Z David Kalnischkies david@kalnischkies.de 2016-04-08T10:50:08Z urn:sha1:40703260cdb40409e930a53a04a4061cf2173f42 There is a good chance that the attempt will fail, but if a user mentions certain packages explicitly on the commandline there is a chance that this will consist of a broken system which is resolved by upgrading more packages then just the mentioned. This limitation was not effecting external resolvers.