build architecture should not be hard-coded at ppa install time

Bug #491418 reported by LaMont Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
William Grant
launchpad-buildd
Fix Released
Undecided
William Grant

Bug Description

Currently, when a PPA buildd is created, we tell it what architecture it will be building for. In order to change the architecture for the buildd in launchpad, we need to also adjust it on the buildd, or launchpad disables the buildd because of the mismatch.

In reality, launchpad-buildd (and the check from soyuz) only really care that the architecture soyuz wants to use is compatible with the architecture of the machine all (most?) of our ppa buildds are capable of being amd64/i386/lpia buildds as needed.

Eventually, it would be good to see soyuz use underutilized buildds better (throwing more buildds to architecture $foo when it has a large backlog and $bar has none, for example.)

Related branches

Changed in soyuz:
importance: Undecided → Low
tags: added: ppa soyuz-build
Changed in soyuz:
status: New → Triaged
William Grant (wgrant)
Changed in launchpad-buildd:
status: New → In Progress
assignee: nobody → William Grant (wgrant)
William Grant (wgrant)
Changed in launchpad-buildd:
status: In Progress → Fix Committed
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in soyuz:
status: Triaged → Fix Committed
assignee: nobody → William Grant (wgrant)
milestone: none → 10.08
William Grant (wgrant)
Changed in soyuz:
status: Fix Committed → Fix Released
William Grant (wgrant)
Changed in launchpad-buildd:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.