Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.1 2022-06-29T13:30:03Z 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-05-23T08:09:31Z Ronan Desplanques ronan.desplanques@gmail.com 2022-05-23T07:57:10Z urn:sha1:cacdb54953dbc81eecf4c3a55c132836e7849098 Before this patch, the expression `Res - File.length()` that was used as the length underflowed. It was very unlikely to cause any problem given the saturating behavior of the std::string constructor that's used. Replacing `Res - File.length()` with `File.length() - Res` would have worked, but omitting the last argument altogether invokes an std::string constructor which does the right thing. 2022-05-11T16:02:07Z David Kalnischkies david@kalnischkies.de 2022-05-11T16:02:07Z urn:sha1:701a501fb1c84296d2003c0092e4308742079591 /dev might not be populated for example in unshare chroots, so just using a temporary file it is until triehash supports non-file input. Regression-Of: f6438ea9e726a1c13ce8d90ac78cc272346ab0f8 Gbp-Dch: Ignore 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-22T15:05:36Z urn:sha1:320245536a7ad21606286d9dcf54acf3bdf096c6 Some of our headers use APT_COMPILING_APT trickery to avoid exposing too broadly details we don't want external clients to know and make use of. The flip-side is that this can lead to different compilation units seeing different definitions if they aren't all using the same config. 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-21T01:01:22Z urn:sha1:8fd65748589bb1e0b671d4a291521bfba1664c5c Our public interface doesn't use zlib for quite a while now so lets drop the last remnants as hopefully nobody depends on us bringing it in… Unlike our own private lib for transitive provision of unistd.h. References: 680b916ce7203a40ebd0a3882b9a71ca77278a67 2022-05-06T16:20:52Z Julian Andres Klode jak@debian.org 2022-05-06T16:20:52Z urn:sha1:97f16727b50dcaa4810e80d3c16639e0ce6a0958 Consistently dealing with fields via pkgTagSection::Key See merge request apt-team/apt!233 2022-05-06T16:20:00Z Julian Andres Klode jak@debian.org 2022-05-06T16:20:00Z urn:sha1:6778e2d672d84c962a578f6de415c666b9cf6ee1 Avoid use of deprecated std::iterator (twice) See merge request apt-team/apt!232 2022-04-07T11:19:52Z Julian Andres Klode julian.klode@canonical.com 2022-04-06T11:51:08Z urn:sha1:824651ded0bcf8603e9b508860b8fe5a68fc53ff The kernel autoremoval algorithm was written to accomodate for Ubuntu's boot partition sizing, which was written to accomodate 3 kernels - 2 installed ones + a new one being unpacked. It seems that when the algorithm was designed, it was overlooked that it actually kept 3 kernels. LP: #1968154