On Sat, Apr 04, 2026 at 11:41:37PM +0200, Agustin Martin wrote: > El jue, 2 abr 2026 a las 19:26, Agustin Martin (<[email protected]>) > escribió: > > > > On Sat, Feb 14, 2026 at 08:57:29PM +0200, Adrian Bunk wrote: > > > Source: ipp-usb > > > Version: 0.9.30-1 > > > Severity: serious > > > Tags: ftbfs > > > > > > https://buildd.debian.org/status/logs.php?pkg=ipp-usb&ver=0.9.30-1 > > > > > > ... > > > === RUN TestTCPClientUIDIp4 > > > tcpuid_test.go:32: lo: > > > tcpuid_test.go:34: 127.0.0.1/8 > > > tcpuid_test.go:34: ::1/128 > > > tcpuid_test.go:94: TCPClientUID("127.0.0.1:51898","127.0.0.1:44853"): > > > NLMSG_ERROR: no such file or directory > > > --- FAIL: TestTCPClientUIDIp4 (0.01s) > > > === RUN TestTCPClientUIDIp6 > > > tcpuid_test.go:32: lo: > > > tcpuid_test.go:34: 127.0.0.1/8 > > > tcpuid_test.go:34: ::1/128 > > > tcpuid_test.go:94: TCPClientUID("[::1]:38622","[::1]:37583"): > > > NLMSG_ERROR: no such file or directory > > > --- FAIL: TestTCPClientUIDIp6 (0.01s) > > > === RUN TestUsbAddrListAddFind > > > --- PASS: TestUsbAddrListAddFind (0.00s) > > > === RUN TestUsbAddrListAddCommutative > > > --- PASS: TestUsbAddrListAddCommutative (0.00s) > > > === RUN TestUsbAddrListDiff > > > --- PASS: TestUsbAddrListDiff (0.00s) > > > === RUN TestUUIDNormalize > > > --- PASS: TestUUIDNormalize (0.00s) > > > FAIL > > > FAIL github.com/OpenPrinting/ipp-usb 0.021s > > > FAIL > > > dh_auto_test: error: cd _build && go test -vet=off -v -p 6 > > > github.com/OpenPrinting/ipp-usb returned exit code 1 > > > make: *** [debian/rules:6: binary-arch] Error 25 > > > > Hi, Adrian, > > > > This package seems to build successfully in my just upgraded amd64 sid > > cowbuilder chroot. May be this was a temporary problem in the build systems > > (last attempts with 0.9.31 happened one month ago and all but one failed). > > Hi, > > Tried in a third amd64 box, now with cowbuilder and sbuild. In both > cases package built successfully. However, build was requeued in most > autobuilders and keep failing there. > > I wonder what is the difference in loopback device between sbuild in > user box and sbuilt in autobuilders that is causing ipp-usb to fail > building in all autobuilders (but loong64), while building in all > amd64 boxes I tried. Are autobuilders more restrictive about ports?
Hi all, Sorry for being this insistent/boring, but I have just noticed that this package with this very same version also builds successfully in Ubuntu autobuilders, https://launchpad.net/ubuntu/resolute/+package/ipp-usb So, seems that is only failing to build in most (but loon64) of our autobuilders. I wonder if loong64 being the last autobuilder set (and may be with different defaults) might be related to this success (and failure in other autobuilders). -- Agustin
