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

Re: StrongARM tactics

On Tue, Dec 06, 2005 at 05:21:46PM -0800, Blars Blarson wrote:
> In article <[🔎] 20051206091400.GA17882@tennyson.dodds.net> vorlon@debian.org writes:
> >Um... no.  This is *porter* work; one does not have to be a buildd admin to
> >analyze a build failure to see whether the package belongs in P-a-s, and
> >there's no reason that the buildd admins alone should bear the
> >responsibility for figuring out whether a permanent build failure should be
> >fixed or ignored.  (Maintainers probably need to be involved in this
> >process, but usually maintainers don't have the requisite knowledge about
> >all our ports to make informed decisions on their own.)

> I can do the analyzing, but what should I do with the results?
> sparc@buildd.debian.org seems to be a black hole.  You'll need to find
> someone willing to communicate with access to the buildd queues before
> the porters can do anything.

I said that deciding which packages should belong in P-a-s is porter work;
as is filing bugs on failed packages that shouldn't, providing patches, and
doing porter NMUs if necessary.

If the porters do this effectively, there's really not much need at all for
telling the buildd maintainers about transient build failures, because
they'll be pretty obvious (and account for the majority of failures, as it
should be).

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: