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

Re: Getting the buildds to notice new architectures in a package




"Wouter Verhelst" <wouter@debian.org> wrote in message 20060716161101.GH18131@country.grep.be">news:20060716161101.GH18131@country.grep.be...
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.

<$arch@buildd.debian.org>. I just committed a change to the
wanna-build-states page to that effect.

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>

That says:
However, wanna-build does not look at the control file of a package when creating its database;
only at the packages' name and section, its urgency, and its priority.

Shouldn't wanna-build use the control file? It would then mean that the lists of packages-arch-specific would not be needed, except in the case of a single version override in the event that a package's control file accidentally listed an architecture on which it is not supported, or failed to list an architecture on which it is supported.



Reply to: