On Sat, 31 Dec 2016 16:44:21 +0100 Mattia Rizzolo wrote:
> On Sat, Dec 31, 2016 at 04:29:47PM +0100, Francesco Poli wrote:
[...]
> > They now risk being auto-removed from testing. If they are indeed
> > auto-removed, they won't re-enter stretch and they won't be part of
> > stretch (as released
On Sat, Dec 31, 2016 at 04:29:47PM +0100, Francesco Poli wrote:
> Wait, there's something in your line of reasoning that is not clear to
> me.
>
> Some packages were in the following situation:
>
> testing: version x with no RC bugs
> unstable: version y affected by one or more RC bugs
>
>
On Sat, 31 Dec 2016 15:46:48 +0100 Mattia Rizzolo wrote:
> On Sat, Dec 31, 2016 at 03:37:47PM +0100, Francesco Poli wrote:
[...]
> > It seems a bit unfair that some packages won't be part of stretch, due
> > to a BTS glitch which happened during the last days before the soft
> > freeze.
>
> It's
On Sat, Dec 31, 2016 at 03:37:47PM +0100, Francesco Poli wrote:
> So many RC bugs introduced into testing, due this BTS version tracking
> issue?!?
Yes.
compare this two list of daily testing migration:
regular migration:
https://lists.debian.org/debian-testing-changes/2016/12/msg00043.html
On Fri, 30 Dec 2016 18:57:06 +0100 Mattia Rizzolo wrote:
> On Fri, Dec 30, 2016 at 04:47:30PM +0100, Francesco Poli wrote:
> > In the meanwhile, I see that something changed on the BTS side.
> > But something still appears to be wrong. The RC bug count page [1]
> > claims
> >
> > Number
On Fri, Dec 30, 2016 at 04:47:30PM +0100, Francesco Poli wrote:
> In the meanwhile, I see that something changed on the BTS side.
> But something still appears to be wrong. The RC bug count page [1]
> claims
>
> Number concerning the current stable release: 597
> Number concerning the next
On Thu, 29 Dec 2016 16:40:39 +0100 Emilio Pozuelo Monfort wrote:
> On 29/12/16 16:34, Francesco Poli wrote:
[...]
> > As of now, the RC bug count page [1] claims
> >
> > Number concerning the current stable release: 24
> > Number concerning the next release: 25
> >
> > which is obviously
On 29/12/16 16:34, Francesco Poli wrote:
> Hello!
> It seems to me that the BTS version tracking is no longer working
> correctly.
>
> Yesterday the RC bug count page [1] suddenly reported more than 2000 RC
> bugs closed or downgraded. The actual listed RC bugs were not really
> closed or
Hello!
It seems to me that the BTS version tracking is no longer working
correctly.
Yesterday the RC bug count page [1] suddenly reported more than 2000 RC
bugs closed or downgraded. The actual listed RC bugs were not really
closed or downgraded, they just seemed to lack knowledge about which
9 matches
Mail list logo
