Source packages which don't produce armhf binaries are being selected as candidates
Bug #1465318 reported by
Francis Ginther
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Touch Boottest |
New
|
Undecided
|
Unassigned | ||
Bug Description
The source packages qtmir-gles and qtubuntu-gles were selected as phone boottest candidates despite not directly producing and armhf binaries. These are supposed to fail the candidate check and not make it to the boottest test itself.
When this happens, the following will be visible on the test console log:
Version tested: ERROR: No packages to install!
[Examples]
http://
http://
Revision history for this message
| Francis Ginther (fginther) wrote | #1 |
To post a comment you must log in.
Did a quick check on this and the problem is that qtmir-gles and qtubuntu-gles both produce binaries that match the name of a binary on the phone (qtmir-android and qtubuntu-android). The armhf binaries are supplied by qtmir and qtubuntu. So this isn't a complete failure of the candidate selection code, just a failure under the specific conditions of a binary name used in multiple packages.