source.list for armhf includes trusty-security which does not exist for arm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Michael Hudson-Doyle |
Bug Description
[Impact]
The armhf cloud image fails during apt-update as the source.list includes a reference to trusty-security, a source that does not appear to host support for that architecture:
http://
This issue is blocking the use of the armhf version of ubuntu on docker hub's official library:
https:/
The latest image possesses this issue,
but might want to check other image architecture and suites as well:
Image: ubuntu-
SHA256SUM: c264a88662bbb1d
Link: https:/
[Test Case]
Unpack the armhf chroot and attempt to run apt-get update in it. If it succeeds, this bug is fixed.
[Regression Potential]
Part of the verification should be to diff the trees produced by versions of livecd-rootfs in -updates and -proposed. The only non-trivial difference should be in /etc/apt/
Related branches
- Ubuntu Core Development Team: Pending requested
-
Diff: 37 lines (+13/-6)2 files modifieddebian/changelog (+7/-0)
live-build/auto/build (+6/-6)
description: | updated |
tags: | added: docker partner-images |
tags: | added: id-59e4f7322915e8534b646c46 |
Changed in livecd-rootfs (Ubuntu): | |
assignee: | Dimitri John Ledkov (xnox) → Michael Hudson-Doyle (mwhudson) |
assignee: | Michael Hudson-Doyle (mwhudson) → nobody |
status: | Confirmed → Fix Released |
Changed in livecd-rootfs (Ubuntu Trusty): | |
status: | Confirmed → In Progress |
assignee: | Dimitri John Ledkov (xnox) → Michael Hudson-Doyle (mwhudson) |
Changed in livecd-rootfs (Ubuntu Trusty): | |
status: | In Progress → Triaged |
description: | updated |
Changed in livecd-rootfs (Ubuntu Trusty): | |
status: | Triaged → In Progress |
tags: |
added: targetmilestone-inin14044 removed: targetmilestone-inin--- |
I can confirm that this is happening, and it's in the output that comes from the buildds, so it's a livecd- rootfs/ live-build bug.
(It's probably the former, so adding that package to this bug.)