Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.2 2022-07-24T13:44:13Z 2022-07-24T13:44:13Z Julian Andres Klode julian.klode@canonical.com 2022-07-24T13:44:13Z urn:sha1:518746f7e03115eb7bdf894d23e74ae115c8717b 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 2021-11-17T16:32:18Z Julian Andres Klode julian.klode@canonical.com 2021-11-17T15:29:09Z urn:sha1:891efe3b201a104445ea723a3a5b9b434a78c364 Suggesting the removal of Essential and Protected packages as a solution leads to situations where YouTubers end up removing their desktop. Let's not remove such packages ourselves. 2021-10-18T13:37:47Z Julian Andres Klode jak@debian.org 2021-10-18T13:37:47Z urn:sha1:efa3528de4277a3d5195c5ce875e7ee960726239 Add AllowRange option to disable HTTP Range usage See merge request apt-team/apt!188 2021-09-16T20:38:46Z David Kalnischkies david@kalnischkies.de 2021-09-16T17:33:24Z urn:sha1:61c1d7d3658fdcd4b32f8b071cef7941120f8abc apt makes heavy usage of HTTP1.1 features including Range and If-Range. Sadly it is not obvious if the involved server(s) (and proxies) actually support them all. The Acquire::http::AllowRange option defaults to true as before, but now a user can disable Range usage if it is known that the involved server is not dealing with such requests correctly. 2021-09-04T14:20:12Z David Kalnischkies david@kalnischkies.de 2021-09-04T14:10:50Z urn:sha1:70c669e2566d119559d2986635bb6c1d0d368073 APT is not the place this information should be stored at, but it is a good place to experiment and see what will be (not) needed in the future for a proper implementation higher up the stack. This is why "BarbarianArchitectures" is chosen instead of a more neutral and/or sensible "VeryForeign" and isn't readily exported in the API to other clients for this PoC as a to be drawn up standard will likely require potentially incompatible changes. Having a then outdated and slightly different implementation block a "good" name would be bad. The functionality itself mostly exists (ignoring bugs) since the introduction of MultiArch as we always had the risk of encountering packages of architectures not known to dpkg (forced onto the system, potentially before MultiArch) we had to deal with somehow and other edge cases. All this commit really does is allowing what could previously only be achieved with editing sources.list and some conf options via a single config option: -o APT::BarbarianArchitectures=foo,bar 2021-07-28T11:08:35Z Julian Andres Klode julian.klode@canonical.com 2021-07-28T10:43:56Z urn:sha1:4001af8920389e2bb2672b673b181c4e92515872 This is very basic support on the testing side, we just test the debug output but not how long it actually took. Would be nice to check time really. 2021-07-28T11:04:10Z Julian Andres Klode julian.klode@canonical.com 2021-07-08T14:49:20Z urn:sha1:121ccd0e0c2612bab9ba5383d5599b54e29e4643 Add a new Item field called FetchAfter, which determines the earliest time the item should be fetched at. Adjust insertion into queue to take it into account alongside priority, and only fill pipelines with items that are ready. 2021-04-13T15:52:07Z Julian Andres Klode julian.klode@canonical.com 2021-04-13T15:52:07Z urn:sha1:9d95c64be8dd5a74efb7bcd134f6425c837c22ca It defaults to false, like the other options there do. 2021-04-13T14:00:41Z Julian Andres Klode julian.klode@canonical.com 2021-04-09T16:16:10Z urn:sha1:1412cf51403286e9c040f9f86fd4d8306e62aff2 Repositories without Size information for packages are not proper and need fixing. This ensures people see an error in CI, and get notifications and hence the ability to fix it. It can be turned off by setting Acquire::AllowUnsizedPackages to true.