On Mon, Jul 18, 2016 at 07:41:54PM +0200, Andreas Metzler wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: britney
>
> Hello,
>
> I have been wondering why hugin 2016.2.0~rc1+dfsg-2 (urgency=low) will
> be considered for testing migration after only 5 days and I think I found
> the reason.
>
> Testing has 2016.0.0+dfsg-1, which was followed by
> [2016-07-16] 2016.2.0~rc1+dfsg-2 in unstable (low)
> [2016-07-11] 2016.2.0~rc1+dfsg-1 in experimental (low)
> [2016-06-04] 2016.2.0~beta1+dfsg-1 in experimental (medium)
>
> britney seems to have remembered that 2016.2.0~beta1+dfsg-1 had medium
> urgency and chose to consider this urgency for sid->testing migration.
>
> I think that is a bug, especially as dch uses medium by default for
> uploads to experimental.
>
> cu Andreas
Does it remember or does it parse the changelog and use the highest
priority since the version in testing? The hugin changelog contains
the urgency=medium entry so this seems a valid urgency to use.
MfG
Goswin
