Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.14 2024-02-20T12:49:04Z 2024-02-20T12:49:04Z Julian Andres Klode julian.klode@canonical.com 2024-02-20T12:43:08Z urn:sha1:40a75722c43ae24cb9a99d6730a3b25b65819c49 This was automated with sed and git-clang-format, and then I had to fix up the top of policy.cc by hand as git-clang-format accidentally indented it by two spaces. 2021-11-23T19:19:23Z Cameron Katri me@cameronkatri.com 2021-11-23T19:19:23Z urn:sha1:6f35750118a06e9d11e6aa7ab29f4ef01b75898b Darwin systems define TRUE and FALSE as preprocessor macros for use with bool. This conflicts with the enum values causing the compilation to fail. 2021-10-18T13:42:56Z Julian Andres Klode jak@debian.org 2021-10-18T13:42:56Z urn:sha1:ad7bae309a827592aa228af9470c1aa7abdd189e basehttp: Turn HaveContent into a TriState See merge request apt-team/apt!179 2021-09-16T20:40:00Z David Kalnischkies david@kalnischkies.de 2021-09-16T17:48:33Z urn:sha1:d013f8957c0d464e0059cc107ca79d887cf9f8aa Debian buster (oldstable) ships 6.1 while bullseye (stable) ships 6.5 and so the later is 'fixed'. Upstream declares 6.0 still as supported. It might be still a while we encounter "bad" versions in the wild, so if we can detect and work around the issue at runtime automatically we can save some users from running into "persistent" partial files. References: https://varnish-cache.org/docs/6.4/whats-new/changes-6.4.html#changes-in-behavior 2021-09-16T20:38:46Z David Kalnischkies david@kalnischkies.de 2021-09-16T17:33:24Z urn:sha1:61c1d7d3658fdcd4b32f8b071cef7941120f8abc apt makes heavy usage of HTTP1.1 features including Range and If-Range. Sadly it is not obvious if the involved server(s) (and proxies) actually support them all. The Acquire::http::AllowRange option defaults to true as before, but now a user can disable Range usage if it is known that the involved server is not dealing with such requests correctly. 2021-07-01T13:47:48Z Julian Andres Klode julian.klode@canonical.com 2021-07-01T13:38:10Z urn:sha1:fe4201380bd377aebd25bd96a06a7eda6c74a533 Set haveContent to HaveContent::FALSE when Content-Length is 0, and change remaining code to only set it to TRUE if it has not been set so far. Closes: #990281 2021-07-01T13:35:21Z Julian Andres Klode julian.klode@canonical.com 2021-07-01T13:35:21Z urn:sha1:f9e2e914996ce8f0af33d5bfed52e814e0f4a861 We need to be able to set HaveContent to false if the Content-Length is 0, and not have that overriden just because a later header is Content-Type. 2021-04-13T14:00:41Z Julian Andres Klode julian.klode@canonical.com 2021-04-09T16:11:02Z urn:sha1:27a4fb3a9ac67a13ed516c75feefdc1fd426520a The maximum request size is accidentally set to any sized file, so if an unsized file is present, and it turns out to be larger than the maximum size we set, we'd error out when checking if its size is smaller than the maximum request size. LP: #1921626 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. 2021-02-04T10:00:00Z David Kalnischkies david@kalnischkies.de 2020-06-28T18:52:09Z urn:sha1:96dc40b19623621a9cc2c5541fb3adbbceb553b1 varg API is a nightmare as the symbols seems different on ever other arch, but more importantly SendMessage does a few checks on the content of the message and it is all outputted via C++ iostreams and not mixed in FILE* which is handy for overriding the streams.