Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.1.16 2021-01-08T20:48:44Z 2021-01-08T20:48:44Z Julian Andres Klode jak@debian.org 2021-01-08T20:48:44Z urn:sha1:cf2a4ba58c628d15fb308e9a12212e0f11eb27ed Pu/small fixes See merge request apt-team/apt!151 2021-01-08T17:03:08Z Julian Andres Klode julian.klode@canonical.com 2021-01-08T17:03:08Z urn:sha1:24984ac47b0172400e575ad44ed60bb22543298b Gbp-Dch: ignore 2021-01-08T17:02:10Z Julian Andres Klode julian.klode@canonical.com 2021-01-08T17:02:10Z urn:sha1:d43b1a03db9e17c69a15b2838fde69450764727a Gbp-Dch: ignore 2021-01-08T16:58:44Z Julian Andres Klode julian.klode@canonical.com 2021-01-08T16:52:53Z urn:sha1:c7123bea6a8dc2c9e327ce41ddfc25e29f1bb145 People have been asking for a feature to error out on transient network errors for a while, this gives them one while keeping the door open for other modes we need, such as --error-on=no-success which we need to determine when to retry the daily update job. Closes: #594813 (and a whole bunch of duplicates...) 2021-01-08T13:48:47Z Julian Andres Klode julian.klode@canonical.com 2021-01-08T13:43:21Z urn:sha1:bd64bb79537fac17e1474672402d6b0572dce94a If we have different binNMU versions on different architectures, we don't want madness to ensue. This is a change from how update-manager does things, as Ubuntu does not have binNMUs, but I believe it's the right thing to do for a generic solution. 2021-01-08T13:48:47Z Julian Andres Klode julian.klode@canonical.com 2020-08-10T18:16:11Z urn:sha1:c5bc86d45e003905ef411146e66b414d26fb1ff8 This adds support for Phased-Update-Percentage by pinning upgrades that are not to be installed down to 1. The output of policy has been changed to add the level of phasing, and documentation has been improved to document how phased updates work. The patch detects if it is running in a chroot, and if so, always includes phased updates, restoring classic apt behavior to avoid behavioral changes on buildd chroots. Various options are added to control this all: * APT::Get::{Always,Never}-Include-Phased-Updates and their legacy update-manager equivalents to always or never include phased updates * APT::Machine-ID can be set to a UUID string to have all machines in a fleet phase the same * Dir::Etc::Machine-ID is weird in that it's default is sort of like ../machine-id, but not really, as ../machine-id would look up $PWD/../machine-id and not relative to Dir::Etc; but it allows you to override the path to machine-id (as opposed to the value) * Dir::Bin::ischroot is the path to the ischroot(1) binary which is used to detect whether we are running in a chroot. 2021-01-08T12:04:29Z Julian Andres Klode jak@debian.org 2021-01-08T12:04:29Z urn:sha1:bab5f78463de487ab5712ce52f1068ea91d3b8f2 Make immediate configuration optional See merge request apt-team/apt!148 2021-01-08T11:38:23Z Julian Andres Klode julian.klode@canonical.com 2021-01-08T11:36:31Z urn:sha1:c530a192d6a57e091d400cb42f9ce0d5a327ff01 The benefits of immediate configuration are that Essential packages will be configured immediately, so if they are wrongly not working without being configured they won't fail later packages. However, we've reached the point where dependencies on the essential set are too complex for immediate configuration to always work, causing installations to error out at the end, despite having succeeded, because we did not correctly return the error here and did not check for pending errors before running dpkg. Given that we check and configure any packages at the end that have not been configured yet, or fail if we can't configure them; making immediate configuration optional is the best way forward - it orders as it does now, but then does not spuriously fail after having successfully installed everything. Closes: #973305, #188161, #211075, #649588 LP: #1871268 2021-01-07T10:46:40Z Julian Andres Klode jak@debian.org 2021-01-07T10:46:40Z urn:sha1:4d9df23b9c2c7039f2e4e7c19df57bfcdef9502b ?depends patterns and friends See merge request apt-team/apt!146 2021-01-04T09:54:42Z Julian Andres Klode julian.klode@canonical.com 2020-12-17T14:21:17Z urn:sha1:38c49b8adeadf54f147140b3a5db7693e9b9b50f This fixes a problem on Ubuntu systems where the /boot partition has been sized to manage 3 kernels, but does not really work with 4 kernels which was causing problems all over the place.