Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.5 2017-09-09T18:12:15Z 2017-09-09T18:12:15Z Julian Andres Klode jak@debian.org 2017-09-03T12:38:58Z urn:sha1:8d23827be3043daf7fed1b86da1d41578889eaeb When writing a Sources files hashes that were already present in the .dsc were always copied through (or modified), even if disabled. Remove them instead when they are disabled, otherwise we end up with hashes for tarballs and stuff but not for dsc files (as the dsc obviously does not hash itself). Also adjust the tests: test-compressed-indexes relied on Files being present in showsrc, and test-apt-update-weak-hashes expected the tarball to be downloaded when an archive only has MD5 and we are requiring SHA256 because that used to work because the tarball was always included. Closes: #872963 2017-09-09T15:19:48Z David Kalnischkies david@kalnischkies.de 2017-08-28T11:22:58Z urn:sha1:8130f39cf085efcf34bee9e9ce89802b29bb9318 Commit e250a8d8d8ef2f8f8c5e2041f7645c49fba7aa36 implemented the fix and should have included already this testcase for it. Gbp-Dch: Ignore 2017-09-09T12:00:48Z Julian Andres Klode jak@debian.org 2017-09-09T12:00:11Z urn:sha1:4d4459a5548e82224aac778833625358c0801681 gpgv: WARNING: This key is not suitable for signing in --compliance=gnupg mode 2017-08-24T15:44:31Z Julian Andres Klode jak@debian.org 2017-08-24T15:44:31Z urn:sha1:427828d9638c9e5f3550820bd9d71da5d5a0909c It was broken because apt.conf.d was not readable, but that's where the architecture is defined... 2017-08-12T14:03:26Z Julian Andres Klode jak@debian.org 2017-08-12T14:02:45Z urn:sha1:79c0a12d5c2d4fd8e6bfcf3a632a452239c07fe0 This caused a build failure in the test suite. 2017-08-04T11:06:10Z David Kalnischkies david@kalnischkies.de 2017-07-28T16:20:14Z urn:sha1:d108e019d3ca74c31a1ab646ddef5c60744a5e7d If 'apt-ftparchive packages /path/to/files/' (or sources) is used the files to include in the generated index (on stdout) were included in the order in which they were discovered, which isn't a very stable order which could lead to indexes changing without actually changing content causing needless changes in the repository changing hashsums, pdiffs, rsyncs, downloads, …. This does not effect apt-ftparchive calls which already have an order defined via a filelist (like generate) which will still print in the order given by the filelist. Note that a similar effect can be achieved by post-processing index files with apt-sortpkgs. Closes: 869557 Thanks: Chris Lamb for initial patch & Stefan Lippers-Hollmann for testing 2017-07-26T17:09:04Z David Kalnischkies david@kalnischkies.de 2017-07-14T15:07:22Z urn:sha1:8580574ec63fedd39a3ab3b9f0025e08eae5f620 The feature exists for a long while even if we get around to document it properly only now, so we should push for its adoption a bit to avoid the problems its supposed to solve like avoiding usage of non-world readable configuration files as they can cause strange behaviour for the unsuspecting user (like different solutions as root and non-root). 2017-07-26T17:09:04Z David Kalnischkies david@kalnischkies.de 2017-07-14T11:49:33Z urn:sha1:054243fd0febfef5f1ba89f61eed0e6a34c6a25f We detect the effected sources by matching Release info – that has potential by-catch of repositories which have incorrect field values, but those are better fixed now anyhow. The bigger incorrectness is that this message will not only be printed for the Debian services itself but also for all mirrors not under Debian control but serving Debian like more local/private mirrors which will not (directly) shutdown. It is likely through that many of them will follow suite with less visible announcements or break downright if their upstream source disappears, so having false-positives here seems benefitial for the user in the end. 2017-07-26T17:09:04Z David Kalnischkies david@kalnischkies.de 2017-07-07T19:59:01Z urn:sha1:6291fa81da6ed4c32d0dde33fa559cd155faff11 On HTTP Connect we since recently look into the auth.conf file for login information, so we should really look for all proxies into the file as the argument is the same as for sources entries and it is easier to document (especially as the manpage already mentions it as supported). 2017-07-26T17:09:04Z David Kalnischkies david@kalnischkies.de 2017-07-07T14:24:21Z urn:sha1:ea408c560ed85bb4ef7cf8f72f8463653501332c We have support for an netrc-like auth.conf file since 0.7.25 (closing 518473), but it was never documented in apt that it even exists and netrc seems to have fallen out of usage as a manpage for it no longer exists making the feature even more arcane. On top of that the code was a bit of a mess (as it is written in c-style) and as a result the matching of machine tokens to URIs also a bit strange by checking for less specific matches (= without path) first. We now do a single pass over the stanzas. In practice early adopters of the undocumented implementation will not really notice the differences and the 'new' behaviour is simpler to document and more usual for an apt user. Closes: #811181