2.1.19 testing failures on the debian build daemons

Daniel Kahn Gillmor dkg at fifthhorseman.net
Mon Mar 20 19:10:40 CET 2017

On Mon 2017-03-20 12:04:39 -0400, Justus Winter wrote:
> Daniel Kahn Gillmor <dkg at fifthhorseman.net> writes:
>> Thanks for this suggestion!  I'm hoping that the test suite would work
>> in either situation:
>>  a) where the build path is short enough, or
> There is no such thing as a short enough build path.  The days of the
> test suite using obj/tests/openpgp as GNUPGHOME are long gone.  We are
> creating one GNUPGHOME per test, sometimes a test creates ephemeral home
> diretories on its own.
>> 14661 10:21:44.762330 stat("/run/user/1003", {st_mode=S_IFDIR|000, st_size=100, ...}) = 0 <0.000020>
> /run/user/1003 is not writable.

yes, i know.  Some build daemons, which use extremely minimalist chroots
that don't even have /run at all, let alone a writable /run/user/1003 or
whatever.  Should the test suites fail in those cases?  if so, what
do you think i should do about getting newer versions of GnuPG in
debian?  If not, what needs to change?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: </pipermail/attachments/20170320/ad56a31c/attachment-0001.sig>

More information about the Gnupg-devel mailing list