[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: buildd maintainers stuck?



On Tue, Nov 29, 2005 at 07:46:42PM -0800, Thomas Bushnell BSG wrote:

> The initial upload of libcapplet 1:1.5.11-12 failed to build on alpha,
> arm, i386, and mipsel because of a temporarily absent build
> dependency.  This upload occurred over three weeks ago.

> On November 17 I requested that the buildds requeue this build, but
> nothing has happened.  Can the release team please schedule a binNMU
> or do whatever is supposed to happen?

> Likewise, libglade1 1:0.17-5 was uploaded at the same time and failed
> on the same four archs for the same reason.  Again, a request to
> requeue it was sent on November 17, and nothing has happened.

Both requeued and (now) successfully installed.

> Sending mail to <arch>@buildd.debian.org is supposed to work.  Perhaps
> the solution is for these requests to be tracked on archived mailing
> lists and the BTS?  Or is there some other solution other than bugging
> the release managers?

AIUI, the <arch>@buildd.debian.org addresses have a ridiculously low S:N
ratio due to spam; moreover, they already receive build logs for each failed
package build, and are generally quite capable of figuring out the source of
a failure on their own, so receiving a second mail about a failure that's
still in their inbox isn't necessarily all that useful.

You can bug the release managers, but I'd prefer if people only did this in
connection with package builds needed for RC bugfixes.

My preference would be that such requests be sent first to the porters
(either the mailing lists specified on http://www.debian.org/ports/, or the
individual porters mentioned on the wiki pages linked from
http://release.debian.org/etch_arch_qualify.html).  While most of these
porters are not themselves buildd admins, they *are* the people responsible
for the overall health of a given port, and they should definitely be taking
an active role in sorting out build failures for their architecture; so if
they aren't already in a position to batch-proxy such requests to the buildd
maintainers, they darn well ought to get there.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


Reply to: