support armhf architecture

So, AIUI this is trivial to implement in Offspring (just a matter of adding 'armhf' to ARCH_CHOICES), but do we have armhf builders and package archives already?

On 18 November 2011 21:57, Guilherme Salgado
<email address hidden> wrote:
> So, AIUI this is trivial to implement in Offspring (just a matter of
> adding 'armhf' to ARCH_CHOICES), but do we have armhf builders and
> package archives already?

We don't have builders yet. Buildds are building packages and LP has
armhf support.

All of our armel hardware in the datacenters can run armhf binaries on the underlying armel. If offspring has a way to force uname -m or equivalent such that it doesn't use the underlying native model, the builder does not actually need to be running armhf. (We will likely leave the buildds running armel, and switch which architecture they build.)

There's no difference in uname output between armel and armhf; you can just "chroot" into an armhf chroot from an armel system and vice-versa.

For what it's worth there's a small change to enable it for live-build as well. It "should" work with the a40 version I've put together, however it's untested as of yet.

When polling the slaves Offspring will update its database with the information returned by the slaves (name, machine type, etc), but since the slave registered as the armhf builder was actually running armel Offspring changes the machine type of the builder to armel after the first scan and we no longer have anything to build the armhf jobs.