Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.0.2 2020-04-06T08:04:49Z 2020-04-06T08:04:49Z Julian Andres Klode julian.klode@canonical.com 2020-04-06T08:00:23Z urn:sha1:d3133f92205e06f1f04e39c7e74db9efb98df19f Recent GnuTLS 3.6.11 -> 3.6.13 update in Ubuntu broke our test certificate, it's signed with SHA1. Regenerate with SHA2. openssl req -newkey rsa:2048 -x509 -sha256 -days 36500 -nodes -out apt.crt -keyout apt.key -subj "/CN=localhost/O=APT Testcases GmbH/ST=Some-State/C=DE" cat apt.key apt.crt > test/integration/apt.pem 2020-03-21T07:35:26Z David Kalnischkies david@kalnischkies.de 2020-03-21T07:14:15Z urn:sha1:bf46e09f0e4b52b3c71ac20bb11e7511fc16179f While merging apt-pkg and apt-inst libraries the codepath of handling deb files in apt-pkg was adapted to use the 'old' code from apt-inst instead of fork&exec of dpkg-deb -I. The information we get this way forms the main part of the package stanza, but we add a few semi-optional fields to the stanza to make it look and work more like a stanza we got from a repository. Just be careful with the area where these two parts touch as if, hypothetically, we would stip all newlines around the parts, but forget to add a newline between them later, the two lines around the merge would stick a bit too close together forming one which could result in fun parsing errors if this merged line was previously e.g. a well-formed Depends line and has now extra fluff attached. This codepath has a history with too many newlines (#802553) though, so how likely is it really that it will some day lack one you may ask. References: 6089a4b17c61ef30b2efc00e270b0907f51f352a 2020-03-10T09:57:21Z David Kalnischkies david@kalnischkies.de 2020-03-10T09:46:56Z urn:sha1:429effb963fba7529b8ff57d6b0474916d4fed69 Packages from third-party sources do not always follow the established patterns of more properly maintained archives. In that case it was a driver package for a scanner&printer device which has only a minimum of info attached, but also minimal non-installed packages do not include sections, so we really shouldn't assume their availability. 2020-02-16T11:46:09Z Julian Andres Klode julian.klode@canonical.com 2020-02-16T10:45:05Z urn:sha1:9cc0e2cab7c83ede99e21c70f248d884b8930983 This experiment did not turn out sensibly, as some servers do not accept credentials when none are expected and fail, so you cannot mirror such a repository. This reverts commit c2b9b0489538fed4770515bd8853a960b13a2618. 2020-01-30T15:58:23Z Julian Andres Klode julian.klode@canonical.com 2019-04-15T07:40:20Z urn:sha1:4f9c58d25ff52fbb69cd3439fc1484bea47e1566 Since we append a concrete kernel version to each pattern, and then anchor the pattern, let's just pick any package starting with a kernel name (linux-, kfreebsd-, gnumach-), and not worry about linux-headers, linux-tools, etc specifically, as they'll be caught by the generic pattern. LP: #1607845 2020-01-16T10:10:47Z Julian Andres Klode julian.klode@canonical.com 2020-01-16T09:53:05Z urn:sha1:ea4b7921b7e3eadb42be1deab5f343dbba8f29df APT 1.9.6 introduced empty groups by making use of groups to deduplicate package names. This is not normally a problem, but here we assumed that every group has at least one package. This caused a problem because automake was providing automake-1.16 while having the source package automake-1.16. So we found the automake-1.16 group, iterated over its empty package list, trying to store the provides (which hence never happened). LP: #1859952 2020-01-15T22:02:32Z Julian Andres Klode jak@debian.org 2020-01-15T22:02:32Z urn:sha1:087c97b7959acb1f9417b0b02be58709666476dc apt(8): Disable regular expressions and fnmatch See merge request apt-team/apt!95 2020-01-15T21:19:17Z Julian Andres Klode julian.klode@canonical.com 2020-01-15T21:01:54Z urn:sha1:21cb4a9e513ccb6f376fbcaf67957c4851cbbe32 This is the first step. Next step will be to add warnings to apt-get and then remove support there as well. 2020-01-15T21:07:25Z Julian Andres Klode julian.klode@canonical.com 2019-12-04T12:58:38Z urn:sha1:a9916c3faa2b8c6fa288599efec65868d050b0ef Commit 93f33052de84e9aeaf19c92291d043dad2665bbd restricted auth.conf entries to only apply to https by default, but this was silent - there was no information why http sources with auth.conf entries suddenly started failing. Add such information, and extend test case to cover it. 2019-12-06T12:48:07Z Julian Andres Klode julian.klode@canonical.com 2019-12-06T12:46:58Z urn:sha1:05d1549fb65b00137b22159761462626d11bfe73 apt satisfy "" caused a segmentation fault because we were iterating over the characters, checking if the next character was the end of the string; when it could also be the current character. Instead, check whether the next character is before the end of the string, rather than identical to the end.