Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.1.19 2021-02-09T09:45:26Z 2021-02-09T09:45:26Z Julian Andres Klode julian.klode@canonical.com 2021-02-09T09:45:26Z urn:sha1:5a6677429cd87c9a47027f3d8969584083e0ff84 2021-02-09T09:38:48Z Julian Andres Klode jak@debian.org 2021-02-09T09:38:48Z urn:sha1:cb60beb83610783f664da0bbe1cdb7211aaba90f Various patches uplifted from unfinished fuzzer branches See merge request apt-team/apt!158 2021-02-09T09:38:19Z Julian Andres Klode jak@debian.org 2021-02-09T09:38:19Z urn:sha1:4c3383746f2974be5fdec86616f45fd85948a9aa Show 'Done' always for 'Building dependency tree' See merge request apt-team/apt!157 2021-02-04T20:54:43Z Frans Spiesschaert Frans.Spiesschaert@yucom.be 2021-02-04T19:38:51Z urn:sha1:25fbccb5ba5e8748f1be2721609aa04657934f5e Closes: #981883 2021-02-04T19:38:43Z Frans Spiesschaert Frans.Spiesschaert@yucom.be 2021-02-04T19:38:43Z urn:sha1:6abc0701925d42d714d4b743f2d230082e65ed26 Closes: #981885 2021-02-04T10:00:00Z David Kalnischkies david@kalnischkies.de 2021-02-04T08:38:01Z urn:sha1:131d0e3a261076da715102cb79275988cac810d1 The grep for case-insensitive GPG finds also e.g. "/tmp/tmp.Kc5kKgPg0D" which is not the intention, so we simply eliminate the variation of the /tmp directory here from the output to prevent these false positives. Gbp-Dch: Ignore 2021-02-04T10:00:00Z David Kalnischkies david@kalnischkies.de 2021-02-03T23:44:53Z urn:sha1:f4c4ffbacff336c98470123924f81032de4141cc They result in what looks odd: Abhängigkeitsbaum wird aufgebaut.… Fertig Statusinformationen werden eingelesen.… Fertig 2021-02-04T10:00:00Z David Kalnischkies david@kalnischkies.de 2021-02-03T21:41:56Z urn:sha1:a158e78152316f56b1a324a42a2f00f0a8662ac3 Depending on your configured source 25 MB is hardly enough, so the mmap housing the cache while it is build has to grow. Repeatedly. We can cut down on the repeats of this by keeping a record of the size of the old cache assuming the sizes will remain roughly in the same ballpark. 2021-02-04T10:00:00Z David Kalnischkies david@kalnischkies.de 2021-02-03T20:47:00Z urn:sha1:c31ba27ecf7e35e03af34c3d74d3c6c93976f89c APT tries to detect if applying patches is more costly than just downloading the complete index by combining the size of the patches. That is correct for client-side merging, but for server-side merging we actually don't know if we will jump directly from old to current or have still intermediate steps in between. With this commit we assume it will be a jump from old to current through as that is what dak implements and it seems reasonable if you go to the trouble of server side merging that the server does the entire merging in one file instead of leaving additional work for the client to do. Note that this just changes the heuristic to prevent apt from discarding patches as uneconomic in the now more common one merged-patch style, it still supports multiple merged patches as before. To resolve this cleanly we would need another field in the index file declaring which hash we will arrive at if a patch is applied (or a field differentiating between these merged-patch styles at least), but that seems like overkill for now. 2021-02-04T10:00:00Z David Kalnischkies david@kalnischkies.de 2020-06-28T18:59:27Z urn:sha1:3e53dbbe758a4e2da378ebf0296d8105d4a5804c We use the code in error messages, so at least for that edgecase we should ensure that it has sensible content. Note that the acquire system aborts on non-sensible message content in SendMessage, so you can't really exploit this.