apt/apt-pkg/contrib, branch 1.8.0_rc4 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.8.0_rc4 2019-02-10T12:16:27Z Fix various typos in the documentation 2019-02-10T12:16:27Z Jakub Wilk jwilk@jwilk.net 2019-02-10T11:51:30Z urn:sha1:9a702b150c8ddeafa8c10c9f120dafdeb08ef93b Use std::to_string() for HashStringList::FileSize() getter 2019-02-04T14:29:09Z Julian Andres Klode jak@debian.org 2019-01-04T19:48:06Z urn:sha1:780858355914c64793f11860490603c5131c35f1 This slightly improves performance, as std::to_string() (as in gcc's libstdc++) avoids a heap allocation. This is surprisingly performance critical code, so we might want to improve things further in 1.9 by manually calculating the string - that would also get rid of issues with locales changing string formatting, if any. gpgv: Use buffered writes for splitting clearsigned files 2019-02-04T13:43:16Z Julian Andres Klode julian.klode@canonical.com 2019-02-04T13:43:16Z urn:sha1:cde5ee8fe527d3d672775909d27110d11c393774 This is safe here, as the code ensures that the file is flushed before it is being used. The next series should probably make GetTempFile() buffer writes by default. Merge branch 'pu/dead-pin' into 'master' 2019-02-04T12:44:08Z Julian Andres Klode jak@debian.org 2019-02-04T12:44:08Z urn:sha1:3a015964dd56edf897ee062b2eafa2cfc0584380 A pin of -32768 overrides any other, disables repo See merge request apt-team/apt!40 Add a Packages-Require-Authorization Release file field 2019-02-01T16:52:03Z Julian Andres Klode julian.klode@canonical.com 2019-02-01T13:43:52Z urn:sha1:c2b9b0489538fed4770515bd8853a960b13a2618 This new field allows a repository to declare that access to packages requires authorization. The current implementation will set the pin to -32768 if no authorization has been provided in the auth.conf(.d) files. This implementation is suboptimal in two aspects: (1) A repository should behave more like NotSource repositories (2) We only have the host name for the repository, we cannot use paths yet. - We can fix those after an ABI break. The code also adds a check to acquire-item.cc to not use the specified repository as a download source, mimicking NotSource. Drop buffered writing from clearsigned message extraction 2019-02-01T13:08:08Z David Kalnischkies david@kalnischkies.de 2019-02-01T13:08:08Z urn:sha1:8aa2053368d1bb82755164eaa36a10410b434c7c It is dropped in the merged code, but the extraction of the clearsigned message code was the only one who had it previously, so the short-desc explains the change from a before-after merge of the branch PoV. It would make sense to enable it, but as we aren't in a time critical paths here we can delay this for after buster to avoid problems. References: 73e3459689c05cd62f15c29d2faddb0fc215ef5e Suggested-By: Julian Andres Klode Avoid boolean flags by splitting writeTo functions 2019-02-01T13:02:08Z David Kalnischkies david@kalnischkies.de 2019-02-01T13:02:08Z urn:sha1:fd438818d2518901396d6835f845b0b90c3a82fa Suggested-By: Julian Andres Klode Gbp-Dch: Ignore Reuse APT::StringView more in LineBuffer 2019-01-29T15:08:39Z David Kalnischkies david@kalnischkies.de 2019-01-29T14:34:56Z urn:sha1:cd852177246a5ea52ae3fda12b8d991a1ad8d351 No effective change in behaviour, just simplifying and reusing code. Suggested-By: Julian Andres Klode Gbp-Dch: Ignore Rework ifs to use not instead of == false/true 2019-01-29T12:57:19Z David Kalnischkies david@kalnischkies.de 2019-01-29T12:57:19Z urn:sha1:7107b3a056211daf7cd00b130f42168d6aa1e1b6 No change in the logic itself, just dropping "== true", replacing "== false" with not and moving lines around to make branches more obvious. Suggested-By: Julian Andres Klode Gbp-Dch: Ignore Refuse files with lines unexpectedly starting with a dash 2019-01-28T19:45:02Z David Kalnischkies david@kalnischkies.de 2019-01-28T19:45:02Z urn:sha1:9b840b59cc80a072e14b8adc9d76669a7a50ab87 We support dash-encoding even if we don't really work with files who would need it as implementations are free to encode every line, but otherwise a line starting with a dash must either be a header we parse explicitly or the file is refused. This is against the RFC which says clients should warn on such files, but given that we aren't expecting any files with dash-started lines to begin with this looks a lot like a we should not continue to touch the file as it smells like an attempt to confuse different parsers by "hiding" headers in-between others. The other slightly more reasonable explanation would be an armor header key starting with a dash, but no existing key does that and it seems unlikely that this could ever happen. Also, it is recommended that clients warn about unknown keys, so new appearance is limited.