Re: [Piuparts-devel] Piuparts state-dependency-failed-testing analysis

2011-11-01 Thread Dave Steele
On Tue, Nov 1, 2011 at 8:46 AM, Holger Levsen wrote: > Hi Dave, > > ... > > > Here's the output of a script that scrapes > > http://piuparts.debian.org/sid/state-dependency-failed-testing.html and > > analyzes blocking packages: > [...] > > This output says that there are currently 2899 packages

Re: [Piuparts-devel] Piuparts state-dependency-failed-testing analysis

2011-11-01 Thread Holger Levsen
Hi Dave, On Sonntag, 23. Oktober 2011, Dave Steele wrote: > There are currently close to 3000 packages > in state-dependency-failed-testing that can be traced to one or more > state-failed-testing packages. That number actually went down quite a bit > in the last week, when libgtk2.0-bin passed, c

Re: Piuparts state-dependency-failed-testing analysis

2011-10-29 Thread Dave Steele
In the past week, the number of state-dependency-failed-testing has increased by 510, to 3409. Of those, about 80% are blocked by the first package in the list, and 75% are blocked only by that package. On Sat, Oct 22, 2011 at 11:03 PM, Dave Steele wrote: > > I find myself frequently called back

Piuparts state-dependency-failed-testing analysis

2011-10-22 Thread Dave Steele
I find myself frequently called back to the Piuparts waiting-to-be-tested package list at http://piuparts.debian.org/sid/state-dependency-failed-testing.html, and got curious about what is keeping that list as long as it is. Following is an analysis. There are currently close to 3000 packages in s