Bug#816708: marked as done (release.debian.org: migration waits 5 days despite urgency=high)
Your message dated Fri, 04 Mar 2016 18:50:56 +0000
with message-id <1457117456.1948.41.camel@adam-barratt.org.uk>
and subject line Re: Bug#816708: release.debian.org: migration waits 5 days despite urgency=high
has caused the Debian Bug report #816708,
regarding release.debian.org: migration waits 5 days despite urgency=high
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 owner@bugs.debian.org
immediately.)
--
816708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816708
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: britney
Hello Release Team!
I noticed something awkward about the unstable→testing migration
and it seems to me that it's not even the first time I see it...
It appears that the migration waits 5 days, even in cases where the
upload has set urgency=high.
For instance, openssl/1.0.2g-1 hasn't yet migrated to testing:
$ rmadison openssl | grep 'unstable \|testing ' | cut -c 1-60
openssl | 1.0.2d-1 | unstable
openssl | 1.0.2f-2 | testing
openssl | 1.0.2g-1 | unstable
but it got uploaded more than 2 days ago [1]. The excuses [2] seem
to confirm that britney is waiting 5 days.
Since this upload fixes several vulnerabilities, I think the urgency
is well justified: why does britney seem to ignore it?
Please investigate and fix the issue.
Or else, please clarify where my reasoning is wrong.
Thanks for your time.
Bye!
[1] https://tracker.debian.org/news/751911
[2] https://qa.debian.org/excuses.php?package=openssl
--- End Message ---
--- Begin Message ---
On Fri, 2016-03-04 at 19:35 +0100, Francesco Poli (wintermute) wrote:
> I noticed something awkward about the unstable→testing migration
> and it seems to me that it's not even the first time I see it...
>
> It appears that the migration waits 5 days, even in cases where the
> upload has set urgency=high.
> For instance, openssl/1.0.2g-1 hasn't yet migrated to testing:
>
> $ rmadison openssl | grep 'unstable \|testing ' | cut -c 1-60
> openssl | 1.0.2d-1 | unstable
> openssl | 1.0.2f-2 | testing
> openssl | 1.0.2g-1 | unstable
>
> but it got uploaded more than 2 days ago [1]. The excuses [2] seem
> to confirm that britney is waiting 5 days.
>
> Since this upload fixes several vulnerabilities, I think the urgency
> is well justified: why does britney seem to ignore it?
That package version is not in the list of uploads and urgencies fed to
britney by dak (most likely due to dinstall having had some issues
recently), so the default urgency is being used.
I've added a hint so the package should be eligible to migrate in the
next run.
Regards,
Adam
--- End Message ---
Reply to: