Hi, during the year, a src:dnspython change made it so that any software importing that library now requires a valid /etc/resolv.conf with at least one nameserver configured.
This also made it so that something between 50-100 packages now fail to build if the build system doesn't have any working /etc/resolv.conf. I venture to say that this is a very reasonable configuration to have in a build system that tries to be network-disabled. It must be noted that no actual network operation happen, so this doesn't fall into the "no network activity" bucket. This is the bug that was filed against dnspython: https://bugs.debian.org/989171 Do anybody on the list have any opinion on where is the bug, on dnspython, or on the build environment? As the pbuilder maintainer, I've been asked to make it serve a non-working /etc/resolv.conf just to make that bug above moot, so I'm quite biased on the matter myself :) -- 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
