Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.3.1 2021-03-09T12:44:30Z 2021-03-09T12:44:30Z David Kalnischkies david@kalnischkies.de 2021-03-09T12:26:05Z urn:sha1:676f716717b7f138661ee5cb01edb0051f96ca49 Having three different vectors littered over the method to manage various parts of the lifetime of the argument vector we are creating is a bit dangerous as it means a simple code change could result in a desync of these three, so by moving the functionality of them all into a wrapper class should prevent us from making such mistakes. 2021-03-09T12:38:13Z David Kalnischkies david@kalnischkies.de 2021-03-09T10:40:35Z urn:sha1:302b1edcb1afe8098ddc2ddd576e56b898c1d90b 2021-03-09T12:36:52Z David Kalnischkies david@kalnischkies.de 2021-03-09T10:40:59Z urn:sha1:3312607159410eda3c634a0c6fe3c2b1a4fd3cc3 One less thing to remember to do in all branches. 2021-03-09T10:45:08Z David Kalnischkies david@kalnischkies.de 2021-03-09T10:39:29Z urn:sha1:a5346a50c4f3ef15e71c16a9bf88723ae1153776 It is easy to make mistakes while dealing with such macros regardless of how much you guard them, so just using a lambda removes a lot of concerns here basically for free. 2021-02-23T18:10:29Z Julian Andres Klode julian.klode@canonical.com 2021-02-23T17:23:30Z urn:sha1:f8ff3afcd42d8b2e6506bc6f44a894149bf87442 dpkg will be changed in 1.20.8 to not require --force-remove for deconfiguration anymore, but we want to decouple our changes from the dpkg ones, so let's always pass --force-remove-protected when installing packages such that we can deconfigure protected packages. Closes: #983014 2021-02-02T18:56:46Z David Kalnischkies david@kalnischkies.de 2020-12-02T14:51:09Z urn:sha1:f2c087449286812823d06d1b560fa947e438fa0d Explicitly opening a tar member is a bit harder than it needs to be as you have to remove the compressor extension so that it can be guessed here gain potentially choosing the wrong member. Doesn't really matter for deb packages of course as the member count is pretty low and strongly defined, but testing is easier this way. It also finally fixes an incorrectly formatted error message. 2021-01-27T15:17:01Z Julian Andres Klode jak@debian.org 2021-01-27T15:17:01Z urn:sha1:ce2fbbbcd5d81b4cfd60d2a277cbd9ee63d2c1e7 Include all translations when building the cache See merge request apt-team/apt!156 2021-01-27T11:48:58Z Julian Andres Klode julian.klode@canonical.com 2021-01-27T11:31:05Z urn:sha1:ccd952cc8793bc6b866f92912ef0bb51c42eb540 We do download all translations we ever downloaded, but we don't add all of those to the cache, meaning that if we run update with LANG=C, it might still download your de_DE translation, but it won't insert it into the cache, causing your de_DE user to not get translated messages. LP: #1907850 2021-01-22T15:41:12Z Youfu Zhang zhangyoufu@gmail.com 2021-01-22T09:41:22Z urn:sha1:acbe227d50178657d98a609221b1caa5b128d7bb The read-only /dev/null was duplicated to stdout and stderr, causing writes to those descriptors to fail: [pid 260] openat(AT_FDCWD, "/dev/null", O_RDONLY) = 7 [pid 260] dup2(7, 0) = 0 [pid 260] close(5) = 0 [pid 260] dup2(6, 1) = 1 [pid 260] dup2(7, 2) = 2 [pid 260] write(2, "Chrooting into ", 15) = -1 EBADF (Bad file descriptor) [pid 260] chroot("/chroot/") = 0 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.