Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.3.14 2021-11-27T10:22:38Z 2021-11-27T10:22:38Z Ville Skyttä ville.skytta@iki.fi 2021-11-03T22:08:07Z urn:sha1:01eed4234440d82fc52c8186cf4268517bcd28bc 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-18T14:12:54Z Julian Andres Klode julian.klode@canonical.com 2021-06-09T11:22:38Z urn:sha1:3f07f5345ec79702c3c769047452041b2c12953f Extend the Signed-By field to handle embedded public key blocks, this allows shipping self-contained .sources files, making it substantially easier to provide third party repositories. 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-10-18T13:37:47Z Julian Andres Klode jak@debian.org 2021-10-18T13:37:47Z urn:sha1:efa3528de4277a3d5195c5ce875e7ee960726239 Add AllowRange option to disable HTTP Range usage See merge request apt-team/apt!188 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-09-13T14:09:19Z David Kalnischkies david@kalnischkies.de 2021-09-12T22:54:38Z urn:sha1:4e04cbafe7db326b52ee650a4f4ccc3444da6890 The settings used for unwrapping TLS connections depend on the access and hostname we connect to more than what we eventually unwrap. The bugreport mentions CaInfo, but all other https-settings should also apply (regardless of generic or hostname specific) to an https proxy, even if the connection we proxy through it is http-only. Closes: #990555 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.