In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>- sparc: one buildd which is not consistently able to keep up with the
> volume of incoming packages; no backup buildd, no additional porter
> machine.
Second faster machine has been down, reportedly with disk problems.
Even faster replacement machine (with more redunancy) has been
offered. Apparently waiting coordination between doner (who is a DD)
and Debian System Admin team.
Offers of an addional buildd have been refused. Offers of addional
hardware have been ignored or refused.
Binary uploads of packages by a Debian developer trying to help the
situation have been strongly discouraged. (Puting it mildly.)
Exactly what can an ordinary Debian Developer do to fix this
situation? How is it fair to blame the porters when the DSA and
buildd teams refuse offers of help?
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
