Ian mentioned this bug to me and encouraged me to describe some similar problems I have had to deal with in recent versions of gnupg which were not problems in older versions.
I have a gpg wrapper called regpg https://dotat.at/prog/regpg/ It has a test suite that is supposed to work with gnupg 1.4, 2.0, 2.1, and 2.2. For versions 2.1 and above (which make the agent obligatory), the test suite explicitly starts the agent at the beginning of each test script and kills it at the end; it also uses --debug-quick-random to avoid stalls due to bogus entropy accounting. https://git.uis.cam.ac.uk/x/uis/git/regpg.git/blob/HEAD:/t/lib/T.pm#l100 There was also an issue that I had to split the first test script which originally re-initialized the temporary $GPGHOME and generated some test private keys; the re-initialization caused the agent to commit suicide, which caused key generation to fail, so I split it into separate scripts, one to initialize $GPGHOME, and a second one to generate keys (after the shared per-script setup code restarted the agent). Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ - I xn--zr8h punycode Fitzroy: Northeast, backing north, 6 to gale 8. Rough or very rough, becoming high later in northwest. Rain then showers. Good, occasionally moderate.
