From b4c4ef912b806df3bc9a8ca1882a179bf315de13 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Jan 2019 14:23:02 -0400 Subject: [PATCH] followup --- ...ent_4_90bc2857c83afae250834135a5884898._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/7.20181211+git29-gab4a1bed9_fails_tests_during_neurodebian_build/comment_4_90bc2857c83afae250834135a5884898._comment diff --git a/doc/bugs/7.20181211+git29-gab4a1bed9_fails_tests_during_neurodebian_build/comment_4_90bc2857c83afae250834135a5884898._comment b/doc/bugs/7.20181211+git29-gab4a1bed9_fails_tests_during_neurodebian_build/comment_4_90bc2857c83afae250834135a5884898._comment new file mode 100644 index 0000000000..8730fa3f86 --- /dev/null +++ b/doc/bugs/7.20181211+git29-gab4a1bed9_fails_tests_during_neurodebian_build/comment_4_90bc2857c83afae250834135a5884898._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2019-01-21T18:12:13Z" + content=""" +I've fixed the problem I described above. But I don't think it was the +same problem; the neurodebian build log is not complaining about missing +files/directories. + +gpg in the test suite is using a separate home directory, so it starts a +separate gpg-agent process for that. If the test suite is run on a +filesystem where gpg-agent can't work, due say to unix sockets not being +supported, that might be why it fails. +"""]]