Your message dated Thu, 15 Nov 2018 08:05:04 +0100 with message-id <[email protected]> and subject line Re: [Qa-jenkins-dev] Bug#897662: reproducible: is localhost unresolvable in the build chroot? has caused the Debian Bug report #897662, regarding reproducible: is localhost unresolvable in the build chroot? to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 897662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897662 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: jenkins.debian.org Severity: normal dbus has been failing to build on reproducible.debian.org for a while, with test failures. In the version in experimental (which has better diagnostics for unexpected errors in testing) I see[1]: Failed to lookup host/port: "localhost:0": Name or service not known (-2) Is this accurate? Is `getent hosts localhost` something that is expected to fail in the reproducible-builds chroots? If so, I don't think that's a good idea. Resolving arbitrary DNS names and contacting remote machines is not something that a build should be doing; but if we want to run build-time tests for anything that does networking, then I don't think these actions should be counted as network access: * resolving the reserved name "localhost" to 127.0.0.1 and/or ::1 * listening on 127.0.0.0/8 * listening on ::1 * connecting to servers started by the build-time tests on those addresses * generally making use of the "lo" interface I would tend to consider those to be part of the (admittedly loosely-defined) API of a correctly configured Linux system, rather than being networking. As a result, I think build chroots should have a conventional /etc/hosts available. smcv [1] If you read the log, please ignore the org.freedesktop.DBus.Error.AddressInUse part, which appears to be a dbus bug <https://bugs.freedesktop.org/show_bug.cgi?id=106395> but is not important here.
--- End Message ---
--- Begin Message ---On Fri, May 04, 2018 at 12:03:03AM +0100, Simon McVittie wrote: > As a result, I think build chroots should have a conventional /etc/hosts > available. A new pbuilder handling /etc/hosts and making localhost resolvable has just been installed in our nodes. If you see other packages failing due to this please notify us. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
