Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.2 2022-07-24T16:00:08Z 2022-07-24T16:00:08Z Julian Andres Klode julian.klode@canonical.com 2022-07-24T15:59:31Z urn:sha1:2d87af57ea52cb37c60103abb6468e0ad44864ff 2022-07-24T13:44:13Z Julian Andres Klode julian.klode@canonical.com 2022-07-24T13:44:13Z urn:sha1:518746f7e03115eb7bdf894d23e74ae115c8717b 2022-06-30T11:28:23Z Julian Andres Klode julian.klode@canonical.com 2022-06-30T11:27:37Z urn:sha1:01634926847e7c70ce51ea4592d8da0a25d9150d 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: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-20T08:29:09Z Américo Monteiro a_monteiro@gmx.com 2022-05-20T08:26:49Z urn:sha1:5a85469500acea3b797b9b2ddc5d86a3b00c647a Closes: #1011315 2022-05-17T16:50:49Z Julian Andres Klode julian.klode@canonical.com 2022-05-17T15:06:25Z urn:sha1:5a042d8c8e8265fc8b8a123b93cbebc9e345556b 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-19T11:06:44Z urn:sha1:cd92098caa64b7fd30cdc6b5d56bf7e9e17a449e Differentiating between different types of documentation we build helps in better expressing what needs to be done for our arch:any and arch:all packages currently as well. 2022-04-23T23:00:20Z Frans Spiesschaert Frans.Spiesschaert@yucom.be 2022-04-23T22:57:37Z urn:sha1:51bcb140eacd3c42b2b82d3d8946bf236858bbf1 Closes: #1010030 2022-04-08T10:23:25Z Julian Andres Klode julian.klode@canonical.com 2022-04-08T10:22:37Z urn:sha1:72782263dc1e2f65a1ef02f490d897abdcc9885d