Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.6_alpha5 2017-10-05T15:30:25Z 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 2017-06-26T21:31:15Z David Kalnischkies david@kalnischkies.de 2017-06-04T11:47:51Z urn:sha1:fe8c10a39ebc5c42c764516985f000ed8d998c82 We want to kill the agent if its home directory exists at that location, not if it isn't there (leaving an army of processes around). Gbp-Dch: Ignore 2017-01-19T14:59:38Z David Kalnischkies david@kalnischkies.de 2017-01-19T14:14:19Z urn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee Most of them in (old) code comments. The two instances of user visible string changes the po files of the manpages are fixed up as well. Gbp-Dch: Ignore Reported-By: spellintian 2016-12-31T17:24:12Z David Kalnischkies david@kalnischkies.de 2016-12-31T17:24:12Z urn:sha1:ae73a2944a89e0d2406a2aab4a4c082e1e9da3f9 The idea is simple: Each¹ Find*( call starts with a call check if the given option (with the requested type) exists in the whitelist. The whitelist is specified via our configure-index file so that we have a better chance at keeping it current. the whitelist is loaded via a special (undocumented for now) configuration stanza and if none is loaded the empty whitelist will make it so that no warnings are shown. Much needs to be done still, but that is as good a time as any to take a snapshot of the current state and release it into the wild given that it found some bugs already and has no practical effect on users. ¹ not all in this iteration, but many 2016-12-21T18:36:10Z David Kalnischkies david@kalnischkies.de 2016-12-18T16:42:17Z urn:sha1:4ce2f35248123ff2366c8c365ad6a94945578d66 Importing a new secret key into gpg(2) can be increadibly slow which prolongs the test runs significantly – by caching the homedir we gain a significant speedbonus as reimporting already present keys seems like a far less costly operation. Git-Dch: Ignore