On Wed, Sep 08, 2021 at 05:44:34PM +0200, Helmut Grohne wrote: > On Mon, Sep 06, 2021 at 04:39:39PM +0200, Mattia Rizzolo wrote: > > Do anybody on the list have any opinion on where is the bug, on > > dnspython, or on the build environment? > > I concur that the absence of /etc/resolv.conf is a sensible > configuration. Indeed, it is my method-of-choice for implementing > poor-man's network-less builds with sbuild: Delete /etc/resolv.conf. It > doesn't actually prevent network access, but makes accidental network > access very unlikely.
This does not work when software has a built-in fallback IP when no nameserver is configured in /etc/resolv.conf dnspython removing such a built-in fallback IP address and returning an error instead is what caused the breakage in reproducible builds. >... > As such, I err on dnspython being in need of a fix. What kind of fix? Re-adding a default of 127.0.0.1 (or even 8.8.8.8) when no nameserver is found in /etc/resolv.conf ? dnspython is initialized several packages down in the callstack for the failing packages by a concurrent networking library, and I am not aware of any package in this stack doing something unreasonable. > Helmut cu Adrian