On Sun, Jan 13, 2019 at 01:22:18PM +0100, Martin Pitt wrote: > > I'm thus going to assume that the build environments that runs into > > these problems uses network namespaces or similar and doesn't expose > > anything but loopback to the build chroot. > > Indeed, this points out a broken build environment that doesn't have a > loopback > device. [...]
No, not the case. This used to build ok in the past in my autobuilders: Status: successful cockpit_183-1_amd64-20181201T044648Z Status: successful cockpit_183-1_amd64-20181210T093126.625Z Status: successful cockpit_184-1_amd64-20181216T140526.278Z Status: successful cockpit_184-1_amd64-20181226T121643.534Z Status: failed cockpit_184-1_amd64-20190105T051830.660Z Status: failed cockpit_184-1_amd64-20190112T210843.011Z Status: failed cockpit_184-1_amd64-20190112T210843.654Z Status: failed cockpit_184-1_amd64-20190112T210842.534Z Status: failed cockpit_184-1_amd64-20190112T210841.999Z Thanks.
