Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.8.0_rc4 2019-02-04T12:44:08Z 2019-02-04T12:44:08Z Julian Andres Klode jak@debian.org 2019-02-04T12:44:08Z urn:sha1:3a015964dd56edf897ee062b2eafa2cfc0584380 A pin of -32768 overrides any other, disables repo See merge request apt-team/apt!40 2019-02-01T16:52:03Z Julian Andres Klode julian.klode@canonical.com 2019-02-01T13:43:52Z urn:sha1:c2b9b0489538fed4770515bd8853a960b13a2618 This new field allows a repository to declare that access to packages requires authorization. The current implementation will set the pin to -32768 if no authorization has been provided in the auth.conf(.d) files. This implementation is suboptimal in two aspects: (1) A repository should behave more like NotSource repositories (2) We only have the host name for the repository, we cannot use paths yet. - We can fix those after an ABI break. The code also adds a check to acquire-item.cc to not use the specified repository as a download source, mimicking NotSource. 2019-01-23T23:33:16Z David Kalnischkies david@kalnischkies.de 2019-01-23T21:50:45Z urn:sha1:73e3459689c05cd62f15c29d2faddb0fc215ef5e Having many rather similar implementations especially if one is exported while others aren't (and the rest of it not factored out at all) seems suboptimal. 2018-12-26T20:24:20Z Julian Andres Klode jak@debian.org 2018-12-26T11:40:09Z urn:sha1:563fedea263361b0786303f58dccc1a9a733e1d9 We called low-level ParseDepends without an architecture each time, which means each call looked up the native architecture. Store the native architecture in the class and use that when calling low-level ParseDepends from the high-level ParseDepends(). This improves performance for a cache build from 2.7 to 2.5 seconds for me. Also avoid a call when stripping multiarch, as the native architecture is passed in. 2018-12-10T16:31:24Z Julian Andres Klode julian.klode@canonical.com 2018-12-10T15:52:59Z urn:sha1:806e94dcd8dbdf7bf1909657fd4331cfe17b4ab0 This avoids a lot of problems from local installations of scripting languages and other stuff in /usr/local for which maintainer scripts are not prepared. [v3: Inherit PATH during tests, check overrides work] [v2: Add testing] 2018-10-14T19:23:41Z Julian Andres Klode jak@debian.org 2018-10-14T19:23:41Z urn:sha1:b80e48783c183aeaf1d30d898a7743f091d96336 Support subkeys and multiple keyrings in Signed-By options See merge request apt-team/apt!27 2018-10-05T10:45:47Z Julian Andres Klode julian.klode@canonical.com 2018-10-05T10:29:39Z urn:sha1:6675601c81de85b40dc89772c1d6d17f1811c5ba Some post-invoke scripts install packages, which fails because the environment variable is not set. This sets the variable for all three kinds of scripts {pre,post-}invoke and pre-install-pkgs, but we will only allow post-invoke at a later time. Gbp-Dch: full 2018-09-11T11:16:11Z David Kalnischkies david@kalnischkies.de 2018-08-17T09:59:45Z urn:sha1:ff8fa4ab4b80384a9240f0df63181f71077a8d83 If we limit a file to be signed by a certain key it should usually accept also being signed by any of this keys subkeys instead of requiring each subkey to be listed explicitly. If the later is really wanted we support now also the same syntax as gpg does with appending an exclamation mark at the end of the fingerprint to force no mapping. 2018-09-11T11:08:58Z David Kalnischkies david@kalnischkies.de 2018-09-10T19:34:11Z urn:sha1:329c8d5e149465003ea9007661a7af1099c75c43 We are seeing 'processing' messages from dpkg first, so it makes sense to translate them to "Preparing" messages instead of using "Installing" and co to override these shortly after with the "Preparing" messages. The difference isn't all to visible as later messages tend to linger far longer in the display than the ealier ones, but at least in a listing it seems more logical. 2018-09-11T11:08:58Z David Kalnischkies david@kalnischkies.de 2018-09-10T16:43:34Z urn:sha1:f484906eff85c8c9eadc13ce817d8857abdd08e8 The progress reporting relies on parsing the status reports of dpkg which used to repeat being in the same state multiple times in the same run, but by fixing #365921 it will stop doing so. The problem is in theory just with 'config-files' in case we do purge as this (can) do remove + purge in one step, but we remove this also for the unpack + configure combination althrough we handle these currently in two independent dpkg calls.