Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4.2 2016-12-31T01:29:21Z 2016-12-31T01:29:21Z David Kalnischkies david@kalnischkies.de 2016-12-30T23:07:04Z urn:sha1:44ecb8c3579e5ae8828f83530e4151a0ff84d5d6 This can happen e.g. for file: repositories. There is no inherent problem with setting such values internally, but its bad style, forbidden in the manpage and could be annoying in the future. Gbp-Dch: Ignore 2016-07-22T14:04:36Z David Kalnischkies david@kalnischkies.de 2016-07-20T07:03:09Z urn:sha1:e8e5d464623f1c2e1ef96b14e622728bbf4b89af If a user explicitly requests the download of arch:all apt shouldn't get in the way and perform its detection dance if arch:all packages are (also) in arch:any files or not. This e.g. allows setting arch=all on a source with such a field (or one which doesn't support all at all, but has the arch:all files like Debian itself ATM) to get only the arch:all packages from there instead of behaving like a no-op. Reported-By: Helmut Grohne on IRC 2016-07-19T21:06:20Z David Kalnischkies david@kalnischkies.de 2016-07-19T21:06:20Z urn:sha1:36d5299aacb950aeb8cb117fa603abb21643d844 Moving code around into some more dedicated methods, no effective code change itself. Gbp-Dch: Ignore 2016-06-22T12:05:01Z David Kalnischkies david@kalnischkies.de 2016-06-20T18:50:43Z urn:sha1:d03b947b0ce4f87d7d5cc48d4d274ab3bd0b289a Weak had no dedicated option before and Insecure and Downgrade were both global options, which given the effect they all have on security is rather bad. Setting them for individual repositories only isn't great but at least slightly better and also more consistent with other settings for repositories. 2016-06-22T12:05:01Z David Kalnischkies david@kalnischkies.de 2016-03-17T15:36:14Z urn:sha1:ab94dcece2465f824bea80fc9158bf9a028b2e87 APT can be forced to deal with repositories which have no security features whatsoever, so just giving up on repositories which "just" fail our current criteria of good security features is the wrong incentive. Of course, repositories are better of fixing their setup to provide the minimum of security features, but sometimes this isn't possible: Historic repositories for example which do not change (anymore). That also fixes problem with repositories which are marked as trusted, but are providing only weak security features which would fail the parsing of the Release file. Closes: 827364 2016-06-17T16:09:15Z David Kalnischkies david@kalnischkies.de 2016-06-17T11:27:34Z urn:sha1:b90faf2486b977aef0183e38a7f9c535a8a61a34 Merging by URI means that having sources lines with different URI methods results in 'strange' warning and error messages, which aren't very friendly from a user point of view as not encoding the method in the filename is effectivly an implementation detail. Merging by filename removes these messages and makes everything "work" even if it isn't working the way it is configured as the indexes aren't acquired over the method given, but over the first method for this release file (which argueably is an implementation detail stemming from the filename encoding, too). So either direction isn't perfectly "right", but personally I prefer "magic" over strange error messages (and doing a full-circle detection of this with its own messages which would need to be translated feels like way too much effort for dubious gain). Closes: 826944 2016-05-15T17:42:13Z Julian Andres Klode jak@debian.org 2016-05-12T08:04:19Z urn:sha1:71203dbf00cbb259fb59e8daf0543a45394b6623 This fixes comparisons where either the stored or the input string have a trailing comma. 2016-05-15T17:18:15Z Julian Andres Klode jak@debian.org 2016-05-15T17:16:54Z urn:sha1:a9fd02dec56bcb3d7485ae286fad665aeed7cda4 This hopefully makes debugging things easier. 2016-05-10T17:09:19Z Julian Andres Klode jak@debian.org 2016-05-10T17:09:19Z urn:sha1:c7b7d4da7f8b8edd9c3d6b13f0b935853ad8a039 This prevented some sources.list entries from working, an example of which can be found in the test. 2016-05-08T16:15:28Z David Kalnischkies david@kalnischkies.de 2016-05-08T16:03:48Z urn:sha1:39c724b4848ef8d85c8c425f982dda85f0df1277 A frontend like apt-file is only interested in a specific set of files and selects those easily via "Created-By". If it supports two locations for those files through it would need to select both and a user would need to know that implementation detail for sources.list configuration. The "Identifier" field is hence introduced which by default has the same value as "Created-By", but can be freely configured – especially it can be used to give two indexes the same identifier.