Package: ftp.debian.org Seen with the last gcc-7 source only upload to unstable. Apparently the time it takes to build the package is too long, and dak doesn't remember anymore that it saw these packages before, and the packages land in the NEW queue again.
This happened in the past in experimental too, when a build failed on some architecture, and some binary packages were not present anymore in experimental. <doko> gcc-7 for all, amd64, i386 and mips is in "Uploaded" state for 16h. if the builds are lost, could somebody give them back? <aurel32> doko: they are in new <doko> hmm, no new binary packages compared to the last upload ... <ansgar> doko: libn32stdc++-7-dev wasn't in the last upload (it isn't in experimental) <ansgar> Same for other libn32* packages on mips. <ansgar> Or libx32gcc-7-dev on i386 and amd64. <ansgar> Hmm. Maybe gcc-7 got removed from experimental, then the overrides got removed (unused), and the builds only arrived then (making them NEW)? <adsb> also hmm https://buildd.debian.org/status/package.php?p=gcc-7&suite=experimental says no logs <doko> it surely built in the past, on all archs <adsb> 20170618195953|check-overrides|dak|removing unused override|unstable|main|deb|libx32gcc-7-dev|optional|libdevel|None <adsb> so ansgar wins the cookie <ansgar> So dak should be less agressive with removing overrides... <jrtc27> dak wanted to go on a diet <adsb> not sure what's going on with the log view though <ansgar> It has a 14 days delay, but only for new overrides. Unused overrides are removed right away.
