Making schleuder build reproducibly

[Daniel Kahn Gillmor]

On Tue 2017-11-07 17:02:02 +0100, Georg Faerber wrote:

> On 17-11-04 16:01:43, Holger Levsen wrote:
>> On Mon, Oct 30, 2017 at 06:21:39PM +0100, Georg Faerber wrote:
>> > @dkg: It seems, there is still a bug / race in dirmngr, which leads to
>> > errors like "can't connect to '127.0.0.1': no IP address for host" and
>> > in turn "marking host '127.0.0.1' as dead". See the attached debug log for
>> > details, the log was taken on October 1st with dirmrngr out of unstable.
>> > I'm happy to debug this further, if needed.
>> 
>> indeed, random success+failure is visible for 3.2.1-1 on armhf:
>> 
>> https://tests.reproducible-builds.org/debian/rb-pkg/buster/armhf/schleuder.html
>
> I'm actually unsure if these failures are caused by dirmngr, or if it's,
> more likely, failing ruby code. 

I believe it's likely that your local keyserver isn't listening
properly, but dirmngr's errors/warnings are certainly confusing.

I've started a thread over on gnupg-devel to try to clean up the dirmngr
error messages at least.

If you can replicate that sequence of log messages (in particular, the
"Unknown host" weirdness) with a minimal example on some system
configuration, it'd be great to follow up over there.  I've been unable
to replicate it myself with dirmngr 2.2.2-1.

   --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/20171109/737bcfd3/attachment.sig>