Ian Jackson writes ("Re: [pkg-gnupg-maint] Bug#868550: reprepro seems to provide a repro"): > This just happened to me again. The problem persisted even after > git-clean -xdff which deletes the GNUPGHOME directory (since it's in > my source tree). "killall gpg-agent" and then git-clean "fixed" it.
This time it happened in a more controlled invocation and I have a whole slew of logs and things. After the whole test run had "completed" (with many failures), I found this: zealot:2dgit> ps -efH | grep gpg-agent ian 3928 22758 0 14:04 pts/40 00:00:00 grep gpg-agent ian 30388 1 0 13:53 ? 00:00:00 /usr/bin/gpg-agent --debug-quick-random --homedir /home/ian/things/Dgit/2dgit/tests/tmp/tag-updates/gnupg --use-standard-socket --daemon ian 30930 1 0 13:53 ? 00:00:00 /usr/bin/gpg-agent --debug-quick-random --homedir /home/ian/things/Dgit/2dgit/tests/tmp/version-opt/gnupg --use-standard-socket --daemon ian 31235 1 0 13:54 ? 00:00:00 /usr/bin/gpg-agent --debug-quick-random --homedir /home/ian/things/Dgit/2dgit/tests/tmp/trustingpolicy-replay/gnupg --use-standard-socket --daemon zealot:2dgit> If you like I can send you a tarball of the logs (and the relevant dgit source tree). For my reference, I was running my ad-hoc script pretest-to-tested. It was trying to test ab3063a9585ec57b085379bf1485a7b2cb7118cd. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.