Your message dated Mon, 26 Oct 2020 21:34:41 +0100
with message-id <[email protected]>
and subject line Re: dak is removing overrides too early
has caused the Debian Bug report #865304,
regarding dak is removing overrides too early
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
865304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865304
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
On Tue, 20 Aug 2019 19:48:45 +0200 Ivo De Decker <[email protected]> wrote:
> Hi,
>
> On Tue, Jun 20, 2017 at 02:27:55PM +0200, Matthias Klose wrote:
> > 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.
>
> I submitted a merge request that will (hopefully) fix that:
>
> https://salsa.debian.org/ftp-team/dak/merge_requests/152
>
> Thanks,
>
> Ivo
>
>
>
The merge request has been merged about a year ago and I am closing this
bug on the assumption that it fixed the problem (given that there has
been no reports of either issues or resolution).
Please reopen if the problem persists.
~Niels
--- End Message ---
