Hi Sandro-- On Tue 2016-12-06 09:23:41 -0500, Sandro Knauß wrote: > when i started to run the tests for messagelib within debian build dir > gpg-agent fails to start silently. Here the relevant part > > GNUPGHOME=/build/kf5-messagelib-1co6xC/kf5-messagelib-16.04.3/obj-x86_64-linux-gnu/messagecore/autotests/gnupg_home > gpg-agent --daemon test > _pid=`echo GETINFO pid | > GNUPGHOME=/build/kf5-messagelib-1co6xC/kf5-messagelib-16.04.3/obj-x86_64-linux-gnu/messagecore/autotests/gnupg_home > gpg-connect-agent | grep 'D' | cut -d' ' -f2` > > > the output is: > > gpg-agent[26537]: enabled debug flags: ipc > gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' > gpg-connect-agent: waiting for the agent to come up ... (5s) > gpg-connect-agent: waiting for the agent to come up ... (4s) > gpg-connect-agent: waiting for the agent to come up ... (3s) > gpg-connect-agent: waiting for the agent to come up ... (2s) > gpg-connect-agent: waiting for the agent to come up ... (1s) > gpg-connect-agent: can't connect to the agent: File name too long > gpg-connect-agent: error sending standard options: No agent running > > > The test isn't started at all and no error message is logged, that > gpg-agent do not start, this is not nice. I only get the error, what is > wrong, when i use gpg-connect-agent.
I can confirm that this is the case -- the GNUPGHOME needs to fit within
sockaddr_un.sun_path (see unix(7)). In other test suites that use
GnuPG, i've seen deliberately short paths used.
Your GNUPGHOME is 106 characters in the first place, and sun_path is 108
chars. I don't know how to fix this without rearchitecting all of UNIX,
sadly :/
You could work around it by creating a gnupg_home dir for your tests at
the top level of your build tree, and it would fit within the requisite
length.
--dkg
signature.asc
Description: PGP signature
