Making schleuder build reproducibly

[Daniel Kahn Gillmor]

Hi Georg--

On Thu 2017-06-15 21:19:12 +0200, Georg Faerber wrote:

> I really would like to make the build of schleuder, a gpg enabled
> mailing list, reproducible. However, I'm a bit lost on my own, that's
> why I'm searching for input with this mail:
>
> Some of the upstream provided tests check if importing a key from a
> keyserver work. For this, a keyserver is started, bound to localhost to
> mock the behaviour of the keyservers out there. This seems to work
> sometimes [1], sometimes it fails, leading to
>   
> [2] gpg: error retrieving 'admin at example.org' via keyserver: No keyserver available
>
> or 
>
> [2] gpg: connecting dirmngr at '/tmp/schleuder-test/example.org/list4/S.dirmngr' failed: IPC connect call failed

Hm, these seem like they could be failures of either:

 * dirmngr

 * the test/demo keyserver

have you tried instrumenting either of these components of the test
suite to log more data so that you can see why they're failing?

for dimrngr, you'd do something like adding the following to
dirmngr.conf in the example homedir:

    debug-level guru
    log-file /tmp/schleuder-test/example.org/list4/dirmngr.log
    debug 0xffffffff
    verbose

and then in the event of a test failure, dump the contents of
dirmngr.log

I'm not sure how the test/demo keyserver is currently implemented so i'm
not sure how to get better diagnostics from it.

hth,

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20170615/33e668b7/attachment.sig>