Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.6_alpha6 2018-01-03T17:55:41Z 2018-01-03T17:55:41Z David Kalnischkies david@kalnischkies.de 2017-08-12T14:21:13Z urn:sha1:ef9677831f62a1554a888ebc7b162517d7881116 If a method needs a file to operate like e.g. mirror needs to get a list of mirrors before it can redirect the the actual requests to them. That could easily be solved by moving the logic into libapt directly, but by allowing a method to request other methods to do something we can keep this logic contained in the method and allow e.g. also methods which perform binary patching or similar things. Previously they would need to implement their own acquire system inside the existing one which in all likelyhood will not support the same features and methods nor operate with similar security compared to what we have already running 'above' the requesting method. That said, to avoid methods producing conflicts with "proper" files we are downloading a new directory is introduced to keep the auxiliary files in. [The message magic number 351 is a tribute to the german Grundgesetz article 35 paragraph 1 which defines that all authorities of the state(s) help each other on request.] 2017-12-13T22:56:29Z David Kalnischkies david@kalnischkies.de 2017-10-27T17:09:45Z urn:sha1:355e1aceac1dd05c4c7daf3420b09bd860fd169d For deb files we always supported falling back from one server to the other if one failed to download the deb, but that was hardwired in the handling of this specific item. Moving this alongside the retry infrastructure we can implement it for all items and allow methods to use this as well by providing additional URIs in a redirect. 2017-12-13T22:56:29Z David Kalnischkies david@kalnischkies.de 2017-10-25T23:09:48Z urn:sha1:dff555d40bb9776b5b809e06527e46b15e78736c Moving the Retry-implementation from individual items to the worker implementation not only gives every file retry capability instead of just a selected few but also avoids needing to implement it in each item (incorrectly). 2017-11-22T20:35:51Z Julian Andres Klode jak@debian.org 2017-11-19T15:11:33Z urn:sha1:b85851e510bdf13cef770981f76a403bc20b12da We did not strip away profiling messages when we were diffing from stdin (-). Just always write temporary files and strip from them. We also had a problem when stripping ...profiling: from a line and the next line starts with profiling. Split the sed into two calls so we first remove complete profiling: lines before fixing the ...profiling: cases. 2017-10-05T15:30:25Z David Kalnischkies david@kalnischkies.de 2017-08-01T13:22:09Z urn:sha1:012932793ba0ea9398a9acd80593bed8e77cfbfc gpg2 generates keyboxes by default and users end up putting either those or armored files into the trusted.gpg.d directory which apt tools neither expect nor can really work with without fortifying backward compatibility (at least under the ".gpg" extension). A (short) discussion about how to deal with keyboxes happened in https://lists.debian.org/deity/2017/07/msg00083.html As the last message in that thread is this changeset lets go ahead with it and see how it turns out. The idea is here simply that we check the first octal of a gpg file to have one of three accepted values. Testing on my machines has always produced just one of these, but running into those values on invalid files is reasonabily unlikely to not worry too much. Closes: #876508 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-07-26T17:07:56Z David Kalnischkies david@kalnischkies.de 2017-07-26T16:35:42Z urn:sha1:f2f8e89f08cdf01c83a0b8ab053c65329d85ca90 Failing on too much data is good, but we can do better by checking for exact filesizes as we know with hashsums how large a file should be, so if we get a file which has a size we do not expect we can drop it directly, regardless of if the file is larger or smaller than what we expect which should catch most cases which would end up as hashsum errors later now a lot sooner. 2017-06-27T15:46:29Z David Kalnischkies david@kalnischkies.de 2017-06-27T13:54:10Z urn:sha1:fc251c8c9e2a76ab5c350900e9e032830c81e2b3 On Travis CI running tests with code coverage enabled sometimes generates profiling lines, which we filter out for a while now, but that misses lines generated showing progress still causing test failures, so more sed logic is added in the hopes to ignore them. Extends: 58608941e6b58a46109b7cd875716b3d8054c4bf Gbp-Dch: Ignore 2017-06-26T21:31:15Z David Kalnischkies david@kalnischkies.de 2017-04-09T15:18:19Z urn:sha1:0cbe571a44468806af95f3d8661b07b01704eb26 Changes in the past to the buildsystem and the testing framework broke this little helper script – lets fix those problems to restore functionality. Gbp-Dch: Ignore 2017-06-26T21:31:15Z David Kalnischkies david@kalnischkies.de 2017-03-19T13:27:49Z urn:sha1:a8b19aeeb885596912fd8b03e082866b897688fd We setup a "horrible" environment in the apt-key testcase to check all kinds of things, but we really should be making also at least a simple apt update call, as that in turn will call apt-key which is how apt-key is used in the non-testcase world, so that calling should be able to deal with such environments as well. Gbp-Dch: Ignore