On Sat, Jan 12, 2019 at 09:41:49PM +0100, Andreas Henriksson wrote: > It might be a good idea to first just test if all problems vanishes > if builting in a less network restricted environment, [...]
I guess not, because I'm using plain sbuild on a stretch machine, which AFAIK does not have (by default) network restrictions. For completeness, I've put a bunch of my build logs here: https://people.debian.org/~sanvila/build-logs/cockpit/ Also, this started to happen quite recently. This is my build history for buster: 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 Note: I believe this FTBFS problem is "general", but if for whatever reason you can't reproduce it, please contact me privately, I could offer ssh access to a machine where this happens all the time. Thanks.
