Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1_exp16 2015-11-04T17:04:01Z 2015-11-04T17:04:01Z David Kalnischkies david@kalnischkies.de 2015-10-12T19:11:52Z urn:sha1:88a9e3f832ffa9fd64a8c1a4c8a9e1b0509c06bf In b0d408547734100bf86781615f546487ecf390d9 I accidently removed the documentation for Trusted and replaced it with Signed-By instead of adding it. Git-Dch: Ignore 2015-09-14T13:22:19Z David Kalnischkies david@kalnischkies.de 2015-09-14T11:18:29Z urn:sha1:24e8f24e1e94ec3816b0bfc7a05d1c4e3f73248e This changes the semantics of the option (which is renamed too) to be a yes/no value with the special additional value "force" as this allows by-hash to be disabled even if the repository indicates it would be supported and is more in line with our other yes/no options like pdiff which disable themselves if no support can be detected. The feature wasn't documented so far and hasn't reached a (un)stable release yet, so changing it without trying too hard to keep compatibility seems okay. 2015-08-31T09:42:15Z David Kalnischkies david@kalnischkies.de 2015-08-31T09:42:15Z urn:sha1:491f8a5ee6f0b25e464fb814e120a3b94436654f Git-Dch: Ignore 2015-08-27T16:16:50Z David Kalnischkies david@kalnischkies.de 2015-08-27T16:13:00Z urn:sha1:1a3a14ac63b0c4f18de53a7bddcf79d20a5e814f Disabling pdiffs can be useful occasionally, like if you have a fast local mirror where the download doesn't matter, but still want to use it for non-local mirrors. Also, some users might prefer it to only use it for very big indextargets like Contents. 2015-08-27T09:27:45Z David Kalnischkies david@kalnischkies.de 2015-08-27T08:41:19Z urn:sha1:e6a12ff73a2e3246b9e475d9772e88c79a6249f7 While Target{,-Add,-Remove} is available for configuring IndexTargets already, allow Targets to be mentioned explicitely as yes/no options as well, so that the Target 'Contents' can be disabled via 'Contents: no' as well as 'Target-Remove: Contents'. 2015-08-27T09:27:44Z David Kalnischkies david@kalnischkies.de 2015-08-22T14:22:08Z urn:sha1:3a8776a37af38127fb04565959e8e0e449eb04a4 Reported-By: codespell 2015-08-14T12:42:08Z Julian Andres Klode jak@debian.org 2015-08-14T12:42:08Z urn:sha1:2e38192cec76b3b98fe8aeb5a9a1e0fa3573d3a4 Closes: #617445 2015-08-10T15:27:17Z David Kalnischkies david@kalnischkies.de 2015-07-09T22:07:37Z urn:sha1:c2a4a8dded2dfb56dbcab9689b6cb4b96c9999b6 'files' is a bit too generic as a name for a command usually only used programmatically (if at all) by developers, so instead of "wasting" this generic name for this we use "indextargets" which is actually the name of the datastructure the displayed data is stored in. Along with this rename the config options are renamed accordingly. 2015-08-10T15:25:26Z David Kalnischkies david@kalnischkies.de 2015-06-24T17:31:22Z urn:sha1:b0d408547734100bf86781615f546487ecf390d9 Limits which key(s) can be used to sign a repository. Not immensely useful from a security perspective all by itself, but if the user has additional measures in place to confine a repository (like pinning) an attacker who gets the key for such a repository is limited to its potential and can't use the key to sign its attacks for an other (maybe less limited) repository… (yes, this is as weak as it sounds, but having the capability might come in handy for implementing other stuff later). 2015-08-10T15:25:26Z David Kalnischkies david@kalnischkies.de 2015-06-23T15:26:57Z urn:sha1:0741daeb7ab870b4dd62a93fa12a1cf6330f9a72 These options could be set via configuration before, but the connection to the actual sources is so strong that they should really be set in the sources.list instead – especially as this can be done a lot more specific rather than e.g. disabling Valid-Until for all sources at once. Valid-Until-* names are chosen instead of the Min/Max-ValidTime as this seems like a better name and their use in the wild is probably low enough that this isn't going to confuse anyone if we have to names for the same thing in different areas. In the longrun, the config options should be removed, but for now documentation hinting at the new options is good enough as these are the kind of options you set once across many systems with different apt versions, so the new way should work everywhere first before we deprecate the old way.