On Wed, 2023-01-04 at 10:01 -0800, Noah Meyerhans wrote: > On Wed, Jan 04, 2023 at 06:58:30PM +0200, Adrian Bunk wrote: > > https://buildd.debian.org/status/logs.php?pkg=spamassassin&arch=amd64 > > > > ... > > Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all > > Jan 4 03:57:23.255 [3488924] dbg: logger: logging level is DBG > > Jan 4 03:57:23.257 [3488924] dbg: logger: successfully opened file > > log/sa_check_spamd.g3uk5R/d.sa_check_spamd/spamd.err.0.timestamped > > Jan 4 03:57:23.257 [3488924] dbg: logger: successfully added file > > method > > Jan 4 03:57:23.257 [3488924] dbg: spamd: will perform setuids? 0 > > Jan 4 03:57:23.257 [3488924] dbg: spamd: socket module of choice: > > IO::Socket::IP 0.41, Socket 2.033, have PF_INET, have PF_INET6, > > using legacy Socket6::getaddrinfo, AI_ADDRCONFIG is supported > > Jan 4 03:57:23.257 [3488924] dbg: spamd: socket specification: > > "127.0.0.1", IP address: 127.0.0.1, port: 61558 > > server socket setup failed, retry 1: spamd: invalid address for a > > listen socket: "127.0.0.1": Address family for hostname not > > supported > > [...] > I haven't been able to reproduce this on VMs with IPv6-only > networking. > Is the buildd network environment documented anywhere? There's > clearly > something different about it than my test environment, but I haven't > been able to figure out what it is. > > In the meantime, I'm looking into printing more information about the > Network configuration when running these failing tests. See > https://salsa.debian.org/debian/spamassassin/-/commit/531bf8ea45cde94a60852d62ac701f70c0db4b3d > > On my IPv6-only build host, these changes print: > IP-DEBUG: have_inet4 returning false > IP-DEBUG: have_inet6 returning true > IP-DEBUG: Set spamdlocalhost to ::1 > IP-DEBUG: Set spamdhost to ::1 > > > noahm@localhost:~/spamassassin$ ip -4 addr ; ip -4 ro ; dpkg- > buildpackage -uc -us > /tmp/build.log 2>&1 >
One difference at least is that "IPv6-only" buildds *do* have IPv4 networking, but only on lo. As a result, your have_inet4 test will return true: adsb@x86-conova-01:~$ ip --brief -4 a lo UNKNOWN 127.0.0.1/8 adsb@x86-conova-01:~$ perl -MIO::Socket::INET -e '$sock = IO::Socket::INET->new(LocalAddr => "127.0.0.1", Proto => "udp");' -e 'print $sock ? "true\n" : "false\n";' true https://lists.debian.org/debian-devel/2020/07/msg00070.html is a discussion of the general issue from a couple of years ago, which actually includes spamassassin in its list of affected packages. Regards, Adam
