Re: StrongARM tactics
In article <20051206091400.GA17882@tennyson.dodds.net> email@example.com 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?
firstname.lastname@example.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.
>Wonderful. Nice to see that you think P-a-s entries are somebody else's
>problem that should be "handled centrally".
The buildd administrators have made it clear that's the way they want it.
Blars Blarson email@example.com
With Microsoft, failure is not an option. It is a standard feature.