Kevin Mark <[EMAIL PROTECTED]> writes:
> On Sat, Jun 11, 2005 at 07:49:25AM +0200, Goswin von Brederlow wrote:
>
>>
>> For buildds there are 3 mechanisms in place:
>>
>> 1. no auto list of the buildd
>>
>> Per buildd setting to avoid packages not suitable for a specific
>> buildd (e.g. needs m
On Sat, Jun 11, 2005 at 07:49:25AM +0200, Goswin von Brederlow wrote:
>
> For buildds there are 3 mechanisms in place:
>
> 1. no auto list of the buildd
>
> Per buildd setting to avoid packages not suitable for a specific
> buildd (e.g. needs more ram/disk than this buildd has).
>
> 2. not-for
Russ Allbery <[EMAIL PROTECTED]> writes:
> Hello folks,
>
> There was one suggestion in the bug log from Goswin von Brederlow:
>
> | 1. Build-Depend/Conflict on the architecture
> |
> | Build-Depends: type-handling
> | Build-Conflicts: mips, mipsel, ia64
> |
> | That way an attempt to build on a
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> So your package correctly fails to build on unsupported architectures.
> The only problem is wasting buildd time on it -- in this case, the
> correct course of action would be to ask the Packages-arch-specific[1]
> file maintainers to include thi
On Fri, Jun 10, 2005 at 01:58:18AM -0700, Russ Allbery wrote:
> Right now, therefore, the buildds for those four platforms try to build
> every OpenAFS release, install all its dependencies, and then error out in
> the configure script. This is doubtless a bit annoying to the buildd
> admins, is a
On Fri, Jun 10, 2005 at 01:58:18AM -0700, Russ Allbery wrote:
> Hello folks,
>
> I'm working on the next release of the OpenAFS packages, and I'd really
> like to resolve a long-standing annoyance to the buildds that the package
> at present currently causes. But I'm not sure the best way to do i
6 matches
Mail list logo
