Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.1 2022-06-30T11:28:23Z 2022-06-30T11:28:23Z Julian Andres Klode julian.klode@canonical.com 2022-06-30T11:27:37Z urn:sha1:01634926847e7c70ce51ea4592d8da0a25d9150d 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-29T13:41:36Z Julian Andres Klode jak@debian.org 2022-06-29T13:41:36Z urn:sha1:23fe896858dfc7857f2d59c5fd7627332f11c1ff Fix readme typos See merge request apt-team/apt!244 2022-06-29T13:31:42Z Julian Andres Klode jak@debian.org 2022-06-29T13:31:42Z urn:sha1:316c33026b6e7616eab385574f5557c89ccb2c0a Switch from "security.d.o" to "deb.d.o" (matching bullseye release notes) See merge request apt-team/apt!246 2022-06-29T13:30:03Z Julian Andres Klode jak@debian.org 2022-06-29T13:30:03Z urn:sha1:e4230878687c6d9bd3b13552bb2c1053b9d7d7d8 Rewrite phased updates using a keep-back approach See merge request apt-team/apt!245 2022-06-28T12:54:42Z Julian Andres Klode julian.klode@canonical.com 2022-06-28T12:53:14Z urn:sha1:20739359fa936c0851a4c0f37667526d98c22761 If a package is already pinned to a negative value, we should not override this with a positive 1. This causes packages to be installable that were pinned to -1, which is not intended. For this, implement phasing as a ceiling of 1 for the pin instead of a fixed 1 value. An alternative would have been to fix it to NEVER_PIN, but that would mean entirely NEW packages would not be installable while phasing which is not the intention either. LP: #1978125 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 2022-06-24T23:01:10Z Tianon Gravi tianon@debian.org 2022-06-24T23:01:10Z urn:sha1:446966da35828137be86d388105699b9ddff94be Also, this adds "SUITE-updates", which helps show off one of the smaller benefits of deb822-style sources.list (less duplication). 2022-06-17T17:54:36Z Roberto C. Sánchez roberto@debian.org 2022-06-17T17:53:50Z urn:sha1:ba14879e3a5cefc6bc0b507ec3eb5485050651ce 2022-05-24T14:19:04Z Julian Andres Klode jak@debian.org 2022-05-24T14:19:04Z urn:sha1:edffb0ae26935d948ffeb3be229fdcf37d2a1ee1 Fix integer underflow in flExtension See merge request apt-team/apt!240