Processing control commands:
> reopen -1
Bug #831699 {Done: Julien Cristau } [release.debian.org]
release.debian.org: urgency is sticky across dists - low urgency on sid upload
ignored after previous experimental medium-urgency upload
Bug reopened
Ignoring request to alter fixed versions of bug
Control: reopen -1
Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 [dak] Include suite information in UrgencyLog
Control: block -1 by -2
On Tue, Jul 19, 2016 at 07:53:00PM +, Niels Thykier wrote:
> Adam D. Barratt:
> > On Tue, 2016-07-19 at 15:40 +0200, Goswin von
Adam D. Barratt:
> On Tue, 2016-07-19 at 15:40 +0200, Goswin von Brederlow wrote:
>> On Mon, Jul 18, 2016 at 07:41:54PM +0200, Andreas Metzler wrote:
> [...]
>>> 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+d
On Tue, 2016-07-19 at 15:40 +0200, Goswin von Brederlow wrote:
> On Mon, Jul 18, 2016 at 07:41:54PM +0200, Andreas Metzler wrote:
[...]
> > 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
On 2016-07-19 Julien Cristau wrote:
> On Mon, Jul 18, 2016 at 18:51:33 +0100, Adam D. Barratt wrote:
> > On Mon, 2016-07-18 at 19:41 +0200, Andreas Metzler wrote:
[...]
>>> britney seems to have remembered that 2016.2.0~beta1+dfsg-1 had medium
>>> urgency and chose to consider this urgency for s
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 mi
On Mon, Jul 18, 2016 at 18:51:33 +0100, Adam D. Barratt wrote:
> On Mon, 2016-07-18 at 19:41 +0200, Andreas Metzler wrote:
> > 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.
> >
>
On Mon, 2016-07-18 at 19:41 +0200, Andreas Metzler wrote:
> 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.
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+dfs
9 matches
Mail list logo