On Mon 2017-05-01 10:11:51 +0200, Salvatore Bonaccorso wrote: >> HOME=/home/lamby >> LOGNAME=lamby >> SHLVL=1 >> PWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-perl/libgnupg-interface-perl-0.52 >> OLDPWD=/home/lamby/temp/cdt.20170430222311.WuN76MAfhh.db.libgnupg-interface-perl > > I think that's only indirectly a problem by libgnupg-interface-perl. > The testsuite relies on creating a new GNUPGHOME, and to be on the > safe side, this is done below the test directory with a fresh > directory. > > Now for gnupg the following caused the failures in the testsuite: > > https://lists.gnupg.org/pipermail/gnupg-users/2017-January/057444.html > > I'm CC'ing for comment Daniel, who writed the patch to generalize the > testsuite, so it works with GnuPG 2.1 as well.
Looking into this with libgnupg-interface-perl 0.52-6 (experimental), i
can confirm that i've seen this problem, specifically when trying to run
the test suite twice. When running the test suite exactly once it seems
to work out fine, even on paths that are insanely long. I've tested
this with both GnuPG 2.1.18-8 (unstable) and 2.1.21-2 (experimental).
The failures on repeat are presumably because of something related to
the gpg-agent daemon persisting across the tests. I'll look into
invoking "gpgconf --kill all" at the start of the test suite to see
whether that can resolve the issue.
--dkg
signature.asc
Description: PGP signature
