[Tails-dev] Debian 9: Build fails consistently, name resolu…

Delete this message

Reply to this message
Author: Arnaud
Date:  
To: tails-dev
Subject: [Tails-dev] Debian 9: Build fails consistently, name resolution fails sooner or later
Dear Tails,

first, let me quickly introduce myself, I'm Arnaud, part of the
SilentKeys team. Please refer to this mail to remember about SilentKeys
(it was quite a while ago):
https://mailman.boum.org/pipermail/tails-project/2016-April/000488.html

I've been trying to build a Tails image an didn't succeed yet. My
machine is running Debian 9.

As for Tails, I checked out the tag '3.0-beta1', and that's what I'm
trying to build at the moment.

So far, the build always fails sooner or later because of network
failure, and most precisely name resolution failure. A typical log looks
like that:

    Err http://time-based.snapshots.deb.tails.boum.org sid Release.gpg
        Could not resolve 'time-based.snapshots.deb.tails.boum.org'


The failure doesn't always happen at the same point of the build. At
first, I thought it was related to `apt`, but I also experienced in
failure on a `curl` command (when downloading Tor Browser, in
`config/chroot_local-hooks/10-tbb`). I don't have the log anymore, but
it was also a name resolution failure.

I also experienced another problem at provisionning: sometimes the call
`/usr/lib/apt-cacher-ng/expire-caller.pl` (from `setup-tails-builder`)
hangs. It might be related or not, I'm not sure.

I don't think the problem is my internet connectivity. I have a good
connection and never experience this kind of problem in my daily use. I
tried a little test like that in the VM for a while.

    while true; do wget -O /dev/null -nv
time-based.snapshots.deb.tails.boum.org; sleep 5; done


I didn't see any failure.

I had some doubt about `apt-cacher-ng`, so I ran a build without proxy.

    TAILS_BUILD_OPTIONS=noproxy rake build


It failed all the same.

Now I'm a bit stuck. I'm wondering if I should dig on the `libvirt`
side, but I don't find anything related on the net. I'm wondering if I'm
missing something obvious.

If anyone already experienced this kind of error, or have any advice,
that would be great.

Cheers,
Arnaud