architecture 'all' builds are shown as i386

[Jani Monoses]

Report
======

when a source package's binary builds are shown on the right, for arch 'all' it shows i386, implying that other arches FTBFS if one is not aware or forgets that the package is for arch 'all'.

Analysis
========

The underlying cause for this is the restricted set of machines that build -all packages ('nominatedarchindep' - all i386 today) - and this propogates up through the model and display. See bug 158004 and bug 217427 for more information.

It will be hard to address this without interacting with the underlying issues of bug 158004 - bug it may be possible to apply a heuristic to detect when only -all was present (and so only one build queued up) in the interim.

[Celso Providelo (cprov)]

Makes sense to me and might be a simple change in how we present the information. Let's find someone to work on it.

[TJ (tj)]

I suspect I've just been fooled by this. I uploaded a DKMS kernel source package and only saw an 'i386' build. As I'd built the test package on amd64 I thought there was a problem somewhere and kept fiddling with the debian/control settings and uploading revisions.

I also tried "Architecture: source" but that was rejected (although for DKMS packages surely that is strictly correct?

Eventually found this bug whilst thinking the amd64 buildd's had a glitch.

[Robert Collins (lifeless)]

Dropping this to low - its not easy, its not a UI level issue, and its depending on the other bug being done to do efficiently.

[Dražen Lučanin (kermit666)]

I'll just note that I am still experiencing this issue with my Architecture:all package, 7 years after the original bug was submitted.

https://launchpad.net/~kermit666/+archive/ppa/+packages

How and when will I be able to install my package on an amd64 machine? Right now, I am getting this error message:

    E: Unable to locate package popcorn

[Dražen Lučanin (kermit666)]

Ah, OK. I am able to install the package after all (I made the mistake, since the package is actually located under python-popcorn). Still, the information on Launchpad is confusing and initially sent me looking for the error in the wrong place.