On Sun, Jan 29, 2023 at 02:29:23PM +0100, László Böszörményi (GCS) wrote: > Control: tags -1 +confirmed > > On Sun, Jan 29, 2023 at 12:33 PM Adrian Bunk <b...@debian.org> wrote: > > https://buildd.debian.org/status/logs.php?pkg=neon27&arch=amd64 > > > > ... > > auth.................. 3/20 FAIL - retries (line 311: HTTP error: > > Could not resolve hostname `127.0.0.1': Address family for hostname not > > supported) > Is there a way to detect such buildds as a maintainer? What can I do > except notifying upstream and / or disable such tests?
FWIW "127.0.0.1" is hardcoded here: https://sources.debian.org/src/neon27/0.32.5-1/test/utils.c/#L207 Possibly that could be replaced with "localhost" instead, but I'm not sure if using 127.0.0.1 is an attempt at hiding that the code is ipv4-only rather than protocol independent (maybe)... I tried quickly looking at upstream git history if it could confirm my suspicion, but the closest I could find was: https://github.com/notroj/neon/commit/eff6521be537c74511593743bf8665d898e26567 Seems like localhost -> 127.0.0.1 switch was intentional (and done during SVN days?). Maybe someone digging deeper can find "r1910". Regards, Andreas Henriksson