Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.4 2022-10-31T11:12:04Z 2022-10-31T11:12:04Z Julian Andres Klode julian.klode@canonical.com 2022-10-31T11:11:47Z urn:sha1:bd0abd856f1e3e505572f434efafa38254de2f3b 2022-10-28T18:36:16Z quazgar quazgar@posteo.de 2022-10-28T18:36:16Z urn:sha1:bbde59e804ee6d5bb5547071c0c59fd6cfb02d99 2022-09-28T15:34:34Z Julian Andres Klode julian.klode@canonical.com 2022-09-28T15:17:46Z urn:sha1:dccfe14ffb9713fbf320691c0f6cd679f2acf4fc 2022-08-06T12:43:46Z Povilas Kanapickas povilas@radix.lt 2022-08-06T12:43:46Z urn:sha1:5e4d241e273e32cfc72c80526e8951a767efaaeb The documentation currently does not specify whether `apt-get download` verifies the authenticity of downloaded packages or not. The underlying code does verify the authenticity of packages as usual and would fail if the package signature is invalid. Therefore it makes sense to make this guarantee explicit in the documentation, because without it security-conscious users will likely want to recheck the signatures or checksums manually which is not necessary in this case and just wastes time. 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