On Sat, 2007-02-10 at 15:27 +0100, Frank Küster wrote:
> Steve Langasek <[EMAIL PROTECTED]> wrote:
[...]
> > Heck, before m68k was dropped as a factor in package propagation into
> > testing, I was routinely finding bogus dep-waits set by the m68k buildd
> > maintainers themselves, and that's only about a half-dozen people.
> 
> I can name you the reasons why I don't have much of a clue about this (I
> think): 
[...]
> - it's not easy to see what's going on there, and why.  For example, I
>   don't know where I can read what dep-wait means and why and how a
>   package is put in this state.
[...]
> Of course it's difficult to change that.  Someone should write a nice
> page about it, and "someone" is, as usual, a synonym for "not me".

Someone already did, at least for the buildd side -
http://www.debian.org/devel/buildd/ (with specific reference to
http://www.debian.org/devel/buildd/wanna-build-states).

It's linked from http://www.debian.org/devel/, under "Projects",
"Autobuilder network".

There's also, e.g., http://buildd.debian.org/~jeroen/status/ but I'm not
sure if that's directly linked from anywhere.

Adam

Reply via email to