[Piuparts-devel] retesting failed packages more often

[Andreas Beckmann]

On 2011-11-21 04:19, Dave Steele wrote:
> On Sun, Nov 20, 2011 at 3:25 PM, Andreas Beckmann <debian at abeckmann.de> wrote:
>> I tried to look into this yesterday - reporting is not that easy. I
>> reported 2 or three and usertagged around 8 existing ones ...
>> Eventually I put too much work into making these reports...
> 
> I'll admit that I've been coming at this from a different angle.
> Piuparts has automated mechanisms that work OK to flag errors back to
> developers, even without bug reports. I'm thinking that the best bang

Of course I took a first look at the interesting ones: 'due to
unclassified failures'. :-)

> for the buck for Piuparts work comes from making sure that failures
> are found in a timely manner, are assigned to the right package, and
> are free from false positives and other chaff.
> 
> Over the last couple of weeks, I've submitted bug reports representing
> half of the remaining packages in the sid dependency-failed-testing
> queue (excluding perl), and I intend to continue. At the same time, I

That should just need a new tarball and a recheck of perl

Andreas