Michael Biebl [2020-05-16 12:39 +0200]: > Source: cockpit > Version: 219-1 > Severity: serious > > Hi Martin, > > looks like the latest release reliably triggers a FTBFS on arch-all: > > https://buildd.debian.org/status/logs.php?pkg=cockpit&ver=219-1&arch=all > > The relevant part from the build log > ** > cockpit-protocol:ERROR:src/common/test-webserver.c:374:perform_request: > assertion failed (error == NULL): Error resolving > ?2a02:16a8:dc41:100::238:46259?: Name or service not known > (g-resolver-error-quark, 0) > SKIP: test-webserver Bail out! > cockpit-protocol:ERROR:src/common/test-webserver.c:374:perform_request: > assertion failed (error == NULL): Error resolving > ?2a02:16a8:dc41:100::238:46259?: Name or service not known > (g-resolver-error-quark, 0) > Aborted > ERROR: test-webserver process failed: 134
Right, this seems to be an annoying mis-configuration of the new "conova" buildd. The test hasn't changed in a long time, and works fine on every other buildd, architecture, or distribution (Ubuntu, Fedora, RHEL, Arch, etc.) https://buildd.debian.org/status/logs.php?pkg=cockpit&arch=all Buildd admins, is there something weird about conova, like it resolves "localhost" to that IPv6 address, or more likely, "localhost" cannot be resolved in NSS locally and it's trying to resolve it with that DNS server? As a stopgap I'll probably do a locally built all binary upload, but I can't do it right now. Thanks, Martin
