2.1.19 testing failures on the debian build daemons
Werner Koch
wk at gnupg.org
Mon Mar 20 10:34:06 CET 2017
On Sun, 19 Mar 2017 23:48, dkg at fifthhorseman.net said:
> 0 abc123 at testsystem:~$ gpgconf --create-socketdir
> gpgconf: socketdir is '/home/abc123/.gnupg'
> gpgconf: general error
This is probably a failed stat(2). That can be expected if the /run
directy etc does not exits ...
An strace would be very helpful to see exactly what is going wrong.
> d) i can configure the GnuPG package to deliberately skip the parts of
e) We fix how gpgconf is used. Given that a GNUGHOME is set the
regular code to locate the socketdir will use GNUPGHOME which is
what we need. Only gpgconf --create-socketdir is picky about
permissions etc. and tells the user this. I think this is correct
behaviour because the user requested to create a socketdir.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: </pipermail/attachments/20170320/08d2716e/attachment.sig>
More information about the Gnupg-devel
mailing list