Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.1.18 2021-01-13T15:43:04Z 2021-01-13T15:43:04Z Julian Andres Klode julian.klode@canonical.com 2021-01-13T15:43:04Z urn:sha1:34bf934a6275d4c8b21d2571a9d1597a9a4b9c15 Assigning the result of AllocateInMap directly to Ver->d caused Ver->d to be resolved first, and hence if Ver was remapped during the AllocateInMap, we were trying to assign to the old value. Closes: #980037 2021-01-11T10:39:38Z Julian Andres Klode julian.klode@canonical.com 2021-01-11T10:39:38Z urn:sha1:229e73afa4d6e862262f898a7e58942c90939306 We interpreted "cannot detect chroot" as "not a chroot", but it's arguably the better idea to detect it as a chroot, to avoid new behavior from phased updations in situations where it's unclear (no /proc mounted or stuff). 2021-01-11T10:37:11Z Julian Andres Klode julian.klode@canonical.com 2021-01-11T10:37:11Z urn:sha1:edb63b14225c783c673dcac0cc3c60aae076e45c In case we did not find any kernels to protect, the regular expression will be empty, and trying to substr(1) it will fail. 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