Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.5.5 2022-09-02T21:37:58Z 2022-09-02T21:37:58Z David Kalnischkies david@kalnischkies.de 2022-09-02T09:07:58Z urn:sha1:e1f332324f81b589561a9d9bce8a55d4895f26ec The command line is evaluated in two steps: First all packages given are marked for install and as a second step the resolver is started on all of them in turn to get their dependencies installed. This is done so a user can provide a non-default choice on the command line and have it respected regardless of where on the command line it appears. On the other hand, the order in which dependencies are resolved can matter, so instead of using a "random" order, we now do this in the order given on the command line, so if you e.g. have a meta package pulling in non-default choices and mention it first the choices are respected predictably instead of depending on first appearance of the package name while creating the binary cache. I might have "broken" this more than a decade ago while introducing the reworked command line parsing for Multi-Arch, which also brought in the split into the two steps mentioned above which was the far more impactful 'respect user choice' change. This one should hardly matter in practice, but as the tests show, order can have surprising side effects. 2022-09-02T20:32:59Z David Kalnischkies david@kalnischkies.de 2022-08-31T14:08:54Z urn:sha1:009cf61122b7a0ac22b541035a26e6092c9ac529 Reported-By: gcc Gbp-Dch: Ignore 2022-08-08T08:22:50Z David Kalnischkies david@kalnischkies.de 2022-06-09T07:38:04Z urn:sha1:dc25210d889ebbcdfe96bd814a355961e80bccb3 Support for envvar NO_COLOR was added in 2.3.11, but with our own options we can also be a tiny bit more sensible in not overriding an explicit choice to disable colors. References: 400a6895566b67d70bcde43dc8a1cc1c7121f87d 2022-07-11T14:37:35Z Julian Andres Klode julian.klode@canonical.com 2022-07-08T11:37:41Z urn:sha1:e481022470322b50a3289d2397b42b6eeacfc6e7 Because the auto installer now also marks other binaries in the package for upgrade, we do need to run it or we don't mark those for upgrade. 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-22T15:05:36Z urn:sha1:320245536a7ad21606286d9dcf54acf3bdf096c6 Some of our headers use APT_COMPILING_APT trickery to avoid exposing too broadly details we don't want external clients to know and make use of. The flip-side is that this can lead to different compilation units seeing different definitions if they aren't all using the same config. 2022-05-07T08:45:44Z David Kalnischkies david@kalnischkies.de 2022-04-21T01:01:22Z urn:sha1:8fd65748589bb1e0b671d4a291521bfba1664c5c Our public interface doesn't use zlib for quite a while now so lets drop the last remnants as hopefully nobody depends on us bringing it in… Unlike our own private lib for transitive provision of unistd.h. References: 680b916ce7203a40ebd0a3882b9a71ca77278a67 2022-05-06T16:51:05Z Julian Andres Klode jak@debian.org 2022-05-06T16:51:05Z urn:sha1:4fe52f98c7d12bc8fb07411b1c0594a032eadb3a Do not accept arguments for apt-cache dotty, xvcg See merge request apt-team/apt!237 2022-05-06T16:20:52Z Julian Andres Klode jak@debian.org 2022-05-06T16:20:52Z urn:sha1:97f16727b50dcaa4810e80d3c16639e0ce6a0958 Consistently dealing with fields via pkgTagSection::Key See merge request apt-team/apt!233 2022-05-06T16:16:35Z Julian Andres Klode julian.klode@canonical.com 2022-05-06T16:15:19Z urn:sha1:c6dbd6be7b55bd166f0da5d675cb025b1dc16a1d These commands do not actually interpret the same arguments as depends, or any own ones for that matter. Gbp-Dch: full 2022-04-07T16:25:43Z Julian Andres Klode julian.klode@canonical.com 2022-04-07T16:02:55Z urn:sha1:863421c52a0dd5bae66a882f470166d5bf8496dc We forgot to check whether Archive() and Codename() exist in the first place, sigh. Maybe we should return empty strings instead of nullptr. Reported-By: Johannes 'josch' Schauer Marin Rodrigues on IRC