Nathanael Nerode <[EMAIL PROTECTED]> writes:
> So for various reasons the buildd.net status code is not considered ready
> to be integrated on buildd.debian.org, either by its author or by its
> maintainer or by Ryan Murray. Fine, I understand.
>
> Well, after looking at http://buildd.debian.org/~jeroen/status/ ,
> I concur that it's as good a general interface to buildd status as
> buildd.net,
> and much better than the http://buildd.debian.org/ interface.
Where did you find that url?
> (The contact addresses and machine up/down statuses are a valuable part of
> buildd.net which *isn't* there, but that's another matter entirely, which
> requires different and additional work.)
The graphs are also not there. Looking at the graphs gives a very good
overview of the current trends. E.g. if some buildds break down the
needs-build will steadily rise on a single arch only while some
transition will make it rise on all archs. If some chroot is broken
the building will spike. and so on...
Judging the trends from the package list is much harder.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
