[Piuparts-devel] retesting failed packages more often

[Holger Levsen]

Hi Dave,

On Montag, 21. November 2011, Dave Steele wrote:
> 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
> 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
> truly believe that, for instance, eliminating the need for developers
> to parse 30,000 spurious motd warnings provides more value to Debian
> than an equal amount of time writing individual bug reports.

I agree with you with all the above and am very thankful for you submitting 
bug reports!
 
> On that note - how can I go about getting a snapshot of the logs on
> piatti? It would take quite a while to get through the distribution
> with the resources I have available.

I could give you a tarball but actually wget -m works just fine too ;-)


cheers,
	Holger