Debian Developers - Lost of buildd admins ?

Author

Lost of buildd admins ?

Matthias Urlichs

2004-07-17, 5:53 pm

Hi,

is there a list of buildd admins anywhere?

The immediate reason I'm asking is that the latest build of festival was
failed instead of dep-waited on several architectures (sparc, s390, alpha),
and it's somewhat non-obvious whom to ask to correct that.

The secondary reason I'm asking is that I couldn't find it on www.d.o/dev.
(Given my track record WRT finding obvious information, that may or may
not be a true problem...)

Thanks.

--
Matthias Urlichs

--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Andreas Metzler

2004-07-17, 5:53 pm

On 2004-07-17 Matthias Urlichs <smurf@smurf.noris.de> wrote:
> is there a list of buildd admins anywhere?

> The immediate reason I'm asking is that the latest build of festival was
> failed instead of dep-waited on several architectures (sparc, s390, alpha),
> and it's somewhat non-obvious whom to ask to correct that.

Ryan Murray for alpha, Gerhard Tonn for s390 and James Troup for
sparc. Earlier today Martin Michlmayr mentioned $arch@buildd.d.o, but
I had never heard of these before. ;-)

Goswin posted a suggestion for waiting periods today
http://lists.debian.org/debian-deve...7/msg01057.html

> The secondary reason I'm asking is that I couldn't find it on www.d.o/dev.
[...]

I used to grab this from buildd.net (which is now offline) and some ports
have information on http://www.debian.org/ports/. The brute force
method is probably to grab a handful of .changes files from incoming,
check whether they are from autobuilders (Changed-by: foo-buildd) and
check who signed them. ;-)
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"

--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Goswin von Brederlow

2004-07-18, 2:48 am

Andreas Metzler <ametzler@downhill.at.eu.org> writes:

> On 2004-07-17 Matthias Urlichs <smurf@smurf.noris.de> wrote:
>
>
> Ryan Murray for alpha, Gerhard Tonn for s390 and James Troup for
> sparc. Earlier today Martin Michlmayr mentioned $arch@buildd.d.o, but
> I had never heard of these before. ;-)
>
> Goswin posted a suggestion for waiting periods today
> http://lists.debian.org/debian-deve...7/msg01057.html

The waiting period there was for when a package is marked building
without a trace of its outcome.

I think the waiting period is way to high when the package has
finished building (buildd.d.o has the log) and the buildd admin is not
doing his job of processing it. That should not be something that
takes a week on average but should be a day or below.

Given only one buildd admin caring for multiple archs and having a ton
of other work that is more important it certainly comes as no surprice
the buildd work doesn't get done.

I encourage everyone to volunteer to become a buildd admin,
esspecially for those archs with high delays (which are Jameses and
Ryans archs and s390).

> [...]
>
> I used to grab this from buildd.net (which is now offline) and some ports
> have information on http://www.debian.org/ports/. The brute force
> method is probably to grab a handful of .changes files from incoming,
> check whether they are from autobuilders (Changed-by: foo-buildd) and
> check who signed them. ;-)
> cu andreas

The information is on buildd.d.o: http://buildd.debian.org/stats/
You have to download the arch-all.txt files fr each arch and grep
yourself.

But someone has posted an url to a buildd.net alternative specialised
at just showing package(s) status. Grep in the flame war for it.

MfG
Goswin

--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org