apt, branch 1.3_pre3 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3_pre3 2016-08-04T08:25:36Z Release 1.3~pre3 2016-08-04T08:25:36Z Julian Andres Klode jak@debian.org 2016-08-04T08:25:36Z urn:sha1:c69e82559b29171f0dfc66abc8ac236d74f7201e ExecGPGV: Pass current config state to apt-key via temp file 2016-08-03T17:00:01Z Julian Andres Klode jak@debian.org 2016-08-03T16:50:37Z urn:sha1:98f884ebec556bafe6f9650e105fc7c60580e730 Create a temporary configuration file with a dump of our configuration and pass that to apt-key. LP: #1607283 ExecGPGV: Fork in all cases 2016-08-03T16:45:51Z Julian Andres Klode jak@debian.org 2016-08-03T16:45:51Z urn:sha1:81ee750f90bb4d21a0441196ce105f6848633616 ExecGPGV: Rework file removal on exit() 2016-08-03T16:44:27Z Julian Andres Klode jak@debian.org 2016-08-03T16:44:27Z urn:sha1:e0a243f33cd411f730af3c93aff38635c9668f9e Create a local exiter object which cleans up files on exit. gpgv: Unlink the correct temp file in error case 2016-08-03T14:40:14Z Julian Andres Klode jak@debian.org 2016-07-28T10:41:27Z urn:sha1:d0d06f44ed60a3888528d834a799bae86c2978d5 Previously, when data could be created and sig not, we would unlink sig, not data (and vice versa). apt-key: ignore any error produced by gpgconf --kill 2016-07-31T08:29:25Z David Kalnischkies david@kalnischkies.de 2016-07-31T08:29:25Z urn:sha1:215598df84c092f801fe154e510c68fcc263b3ba gpgconf wasn't always equipped with a --kill option as highlighted by our testcases failing on Travis and co as these use a much older version of gpg2. As this is just for cleaning up slightly faster we ignore any error a call might produce and carry on. Use a recent enough gpg2 version if you need the immediate killing… Gbp-Dch: Ignore Reported-By: Travis CI apt-key: kill gpg-agent explicitly in cleanup 2016-07-31T07:56:26Z David Kalnischkies david@kalnischkies.de 2016-07-31T07:27:19Z urn:sha1:4039798d971752325d097bfbdc9011b5e9efd29c apt-key has (usually) no secret key material so it doesn't really need the agent at all, but newer gpgs insist on starting it anyhow. The agents die off rather quickly after the underlying home-directory is cleaned up, but that is still not fast enough for tools like sbuild which want to unmount but can't as the agent is still hanging onto a non-existent homedir. Reported-By: Johannes 'josch' Schauer on IRC prevent C++ locale number formatting in text APIs (try 2) 2016-07-30T08:14:47Z David Kalnischkies david@kalnischkies.de 2016-07-30T07:57:50Z urn:sha1:7303e11ff28f920a6277c159aa46f80c007350bb Followup of b58e2c7c56b1416a343e81f9f80cb1f02c128e25. Still a regression of sorts of 8b79c94af7f7cf2e5e5342294bc6e5a908cacabf. Closes: 832044 edsp: try to read responses even if writing failed 2016-07-29T20:09:06Z David Kalnischkies david@kalnischkies.de 2016-07-29T19:51:43Z urn:sha1:b60c8a89c281f2bb945d426d2215cbf8f5760738 If a solver/planner exits before apt is done writing we will generate write errors. Solvers like 'dump' can be pretty quick in failing but produce a valid EDSP error report apt should read, parse and display instead of just discarding even through we had write errors. if the FileFd failed already following calls should fail, too 2016-07-29T20:09:04Z David Kalnischkies david@kalnischkies.de 2016-07-29T19:39:20Z urn:sha1:02c38073af51802c02bb104d4450e0e112d641ad There is no point in trying to perform Write/Read on a FileFd which already failed as they aren't going to work as expected, so we should make sure that they fail early on and hard.