Wouter Verhelst <[EMAIL PROTECTED]> writes:
> On Sat, Jul 15, 2006 at 10:55:32PM +0200, Ludovic Brenta wrote:
>> Where should I ask for help?  Neither buildd.debian.org nor
>> www.debian.org/devel/buildd, mention where the buildd admins can be
>> reached; and lists.debian.org does not have a "buildd@" list.
>
> <[EMAIL PROTECTED]>. I just committed a change to the
> wanna-build-states page to that effect.

Thanks; I was aware of these, but the problem was not with any one
architecture in particular; it was with Packages-arch-specific.
Luk Claes pointed me to it, and I've submitted a request to the
admins.  (BTW, thanks, Luk.)

It would perhaps be a good idea to mention the existence of
Package-arch-specific, how it works, and who admins it on the
buildd.debian.org front page, don't you think?

Also, I would propose that a list, [EMAIL PROTECTED], or even better, a
pseudo-package, buildd, be created for such issues. buildd would
complement ftp.debian.org as a central place for buildd-related
requests.

>> I will upload ~20 source packages in the next few weeks, adding
>> support for more architectures to each package.  So I'm really looking
>> for a general solution and not one that only applies to asis.
>
> There is no such general solution. See
> <http://www.debian.org/devel/buildd/wanna-build-states#not-for-us>

Thanks.  I had already read that.  It says:

! A package in not-for-us or packages-arch-specific will not leave
! this state automatically; if your package specifically excluded a
! given architecture in its control file previously, but now includes
! more architectures, it must be manually requeued".

But it does not say how I should go about "reque manually".

-- 
Ludovic Brenta.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to