← Back to team overview

launchpad-dev team mailing list archive

Re: Considering change of Architecture: all builders for next release cycle


Would now also be a good time to look through the archive and assess the
various arch:all packages that do not explicitly declare themselves as
Multi-Arch:foreign (and thus not installable as dependencies of foreign
architecture packages?)  Is there a reason for any such arch:all package to
not declare this field at this point?

On Fri, Oct 3, 2014 at 6:42 AM, Colin Watson <cjwatson@xxxxxxxxxx> wrote:

> Hi,
> We've always built "Architecture: all" packages as part of our i386
> builds.  This is beginning to look a bit outdated.  A few packages have
> had difficulty building their architecture-independent components on
> amd64 (usually due to address space limits, I think).  Debian is working
> on Architecture: all autobuilding - it's traditionally been done by the
> developer, but source-only uploads require autobuilding - and my
> understanding is that this is likely to be done on amd64 buildds.
> Building these on amd64 would make no difference to our capacity - all
> our amd64 and i386 builders are shared nowadays anyway - but it's more
> forward-looking and might help a few more packages build cleanly.
> Launchpad only lets us set this when initialising a new series, so we're
> coming close to a decision point.  What would people think about
> switching this to amd64 when we initialise the 15.04 series?
> Thanks,
> --
> Colin Watson                                       [cjwatson@xxxxxxxxxx]
> --
> ubuntu-devel mailing list
> ubuntu-devel@xxxxxxxxxxxxxxxx
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Follow ups