Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.1.exp11 2015-08-27T09:27:45Z 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. 2015-08-10T15:25:26Z David Kalnischkies david@kalnischkies.de 2015-06-22T10:34:11Z urn:sha1:268ffcebb9ae4278b1e3c3f89f8167f229164dbd A specific trust state can be enforced via a sources.list option, but it effects all entries handled by the same Release file, not just the entry it was given on so we enforce acknowledgement of this by requiring the same value to be (not) set on all such entries. 2015-08-10T15:25:26Z David Kalnischkies david@kalnischkies.de 2015-06-21T21:12:24Z urn:sha1:81460e32961bb0b9922bf8a1a27d87705d8c3e51 Having two different formats in the same file is very dirty and causes external tools to fail hard trying to parse them. It is probably not a good idea for them to parse them in the first place, but they do and we shouldn't break them if there is a better way. So we solve this issue for now by giving our deb822 format a new filename extension ".sources" which unsupporting applications are likely to ignore an can begin gradually moving forward rather than waiting for the unknown applications to catch up. Currently and for the forseeable future apt is going to support both with the same feature set as documented in the manpage, with the longtime plan of adopting the 'new' format as default, but that is a long way to go and might get going more from having an easier time setting options than from us pushing it explicitely. 2015-08-10T15:25:26Z David Kalnischkies david@kalnischkies.de 2015-06-21T14:47:53Z urn:sha1:463c8d801595ce5ac94d7c032264820be7434232 We support arch= for a while, now we finally add lang= as well and as a first simple way of controlling which targets to acquire also target=. This asked for a redesign of the internal API of parsing and storing information about 'deb' and 'deb-src' lines. As this API isn't visible to the outside no damage done through. Beside being a nice cleanup (= it actually does more in less lines) it also provides us with a predictable order of architectures as provides in the configuration rather than based on string sorting-order, so that now the native architecture is parsed/displayed first. Observeable e.g. in apt-get output. 2014-08-26T18:49:48Z David Kalnischkies david@kalnischkies.de 2014-07-18T14:42:40Z urn:sha1:5abbf5bbb5ee8717f89cac6ef409c4cec79259f6 Not all are needed for all files at the moment, but the new docbook building hadn't available some of the entities it used as the files weren't correctly copied around in all cases and having the same across the bord makes working with all of them a little easier. Git-Dch: Ignore