Hi, On Tue, Jul 08, 2014 at 03:50:57PM +0200, Gabriele Giacone wrote: > On Tue, Jul 8, 2014 at 1:51 PM, Samuel Thibault <[email protected]> wrote: > > Gabriele Giacone, le Mon 07 Jul 2014 17:04:49 +0200, a écrit : > >> How about scheduling it on Debian infrastructure? Just not to depend > >> on a laptop. > > > > Because I have to connect to various servers to collect the > > informations, and I can't afford letting some servers be allowed to > > connect to some other servers. > > > > Anyway, is this really a problem? This is just temporary, and I don't > > really want to spend some time on finding a way to do it differently, > > while it may not actually pose problem. > > > > Which files are really wanted so badly as to be available every day? > > As I said, summary and out_of_date are fine to update even on crappy > > networks, it's rather things like the graph which is not. > > Personally I'm just interested in summary.txt to get percentages and > out_of_date.txt to compare to old one to get what changed (hint).
About the latter, I agree it is a useful thing to have. But I think the right approach would be to hack buildd.debian.org to provide an RSS feed with the new failed package per architecture. Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
