summaryrefslogtreecommitdiff
path: root/test/integration/test-bug-769609-triggers-still-pending-after-run
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2015-12-18 12:35:43 +0100
committerDavid Kalnischkies <david@kalnischkies.de>2015-12-19 23:04:34 +0100
commit803491dc568d2994745c3c4359f68053f7261658 (patch)
tree11e3ad26d6a199228b7fb2ecb65f15cc0ba6f2de /test/integration/test-bug-769609-triggers-still-pending-after-run
parentbc8f83a5afd858206efe518c31bbb1ac948a39a3 (diff)
avoid triggering gpg2 migration in apt-key
The presents (even of an empty) secring.gpg is indication enough for gpg2 to tigger the migration code which not only produces a bunch of output on each apt-key call, but also takes a while to complete as an agent needs to be started and all that. We workaround the first part by forcing the migration to happen always in a call we forced into silence, but that leaves us with an agent to start all the time – with a bit of reordering we can make it so that we do not explicitly create the secring, but let gpg create it if needed, which prevents the migration from being triggered and we have at least a bit less of a need for an agent. Changes - even to public only keyrings - still require one, but such actions are infrequent in comparison to verification calls, so that should be a net improvement.
Diffstat (limited to 'test/integration/test-bug-769609-triggers-still-pending-after-run')
0 files changed, 0 insertions, 0 deletions