Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.2 2022-09-28T14:32:44Z 2022-09-28T14:32:44Z Julian Andres Klode julian.klode@canonical.com 2022-09-26T10:33:55Z urn:sha1:f93a5aa2daa92255c75865b6f92dddb4b072ff33 When iterating over I's dependencies (which are called Pkg), we accidentally checked if I was Protected() instead of Pkg when deciding whether Pkg can be kept back. LP: #1990684 2022-06-30T11:21:19Z Julian Andres Klode julian.klode@canonical.com 2022-06-30T11:20:45Z urn:sha1:8416bcb58cba0f8b5e8e8d26b71ae838f228111d Pass some package names to upgrade to see that that works Gbp-Dch: ignore 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