** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin14044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security which do
The infrastructure got fixed and https://partner-
images.canonical.com/core/trusty/current now points to builds that have
this bug fixed, hooray.
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
On Mon, Nov 06, 2017 at 11:19:10PM -, ruffsl wrote:
> Could the "current" folder in Index of /core/trusty at https://partner-
> images.canonical.com/core/trusty/ be updated to redirect to 20171102
> instead of 20170817, as it is presently? The docker library ubuntu image
> build is I think poin
Could the "current" folder in Index of /core/trusty at https://partner-
images.canonical.com/core/trusty/ be updated to redirect to 20171102
instead of 20170817, as it is presently? The docker library ubuntu image
build is I think pointed to "current", and I would like to see the fix
released into
This bug was fixed in the package livecd-rootfs - 2.208.15
---
livecd-rootfs (2.208.15) trusty; urgency=medium
* Fix security mirror sources.list entries for non-x86 architectures by
backporting trunk revision 1408. (LP: #1711735)
-- Michael Hudson-Doyle Tue, 31 Oct 2017
10:
I built rootfses for amd64 and armhf out of trusty-proposed:
https://launchpad.net/~cloud-images-release-managers/+livefs/ubuntu/trusty/docker-ubuntu-core/+build/113861
https://launchpad.net/~cloud-images-release-managers/+livefs/ubuntu/trusty/docker-ubuntu-core/+build/113862
I downloaded these a
Hello ruffsl, or anyone else affected,
Accepted livecd-rootfs into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.208.15 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
** Description changed:
+ [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://security.ubuntu.com/ubuntu/dists/trusty-security/
This issue is blocki
** Changed in: livecd-rootfs (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => Michael Hudson-Doyle (mwhudson)
** Changed in: livecd-rootfs (Ubuntu)
Assignee: Michael Hudson-Doyle (mwhudson) => (unassigned)
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => Fix Released
*
** Branch linked: lp:~mwhudson/livecd-rootfs/bug-1711735
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security which does not exist
for arm
T
@bugproxy
Reverse-proxying this bug report bears no meaning. Please do not track
this launchpad issue. If you are experiencing this or a similar issue on
POWER9 please open a new LTC bug report, and proxy it to launchpad
afresh, explaining the issue you have.
--
You received this bug notificatio
--- Comment From cha...@us.ibm.com 2017-10-18 14:00 EDT---
.
** Tags added: architecture-ppc64le bugnameltc-159986 severity-high
targetmilestone-inin---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Tags added: id-59e4f7322915e8534b646c46
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security which does not exist
for arm
To manage notif
This affects the trusty image for arm64 as well, noted at
https://github.com/docker-library/official-images/issues/3583 (which
referred me back here).
** Bug watch added: github.com/docker-library/official-images/issues #3583
https://github.com/docker-library/official-images/issues/3583
--
Yo
It looks to me the ports.ubuntu.com endpoint is receiving updates for
security fixes for non-amd64 architectures: http://ports.ubuntu.com
/ubuntu-ports/dists/trusty-security/multiverse/
As a workaround until this problem is fixed, I've changed the apt repo
definition to ports.ubuntu.com:
$ sed -i
This is still causing quite a _lot_ of downstream pain -- any chance it
could be re-prioritized?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-se
Just checking in to ask if there is anything I could assist for this issue.
Are there any docs on how build a cloud image using the source in livecd-rootfs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
He means simply removing "trusty + armhf" for the "ros" and/or
"gazebo" images, I believe (not for the "ubuntu" image).
The harm this causes is that "apt-get update" fails, which causes the
whole "docker build" to fail.
Here's an example from ppc64el:
W: Failed to fetch
http://security.ubuntu.co
On 10 September 2017 at 08:55, ruffsl wrote:
> Hello Dan, just following up. Any new ideas? I suppose I can modify our
> official docker hub manifest to omit trusty for armhf to at least get
> xenial images out of our farm.
Do not omit trusty for armhf, there are production systems that depend
on
Hello Dan, just following up. Any new ideas? I suppose I can modify our
official docker hub manifest to omit trusty for armhf to at least get
xenial images out of our farm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Unfortunately my change didn't fix the issue; I'll revisit this soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security which does not exist
On Wed, Aug 23, 2017 at 07:10:16PM -, ruffsl wrote:
> Hello Dan, was your latest commit successful in building a cloud image with a
> patched source list?
> https://git.launchpad.net/~daniel-thewatkins/ubuntu/+source/livecd-rootfs/commit/?id=1bc0b2eec50726f46510df4a340d2f27f62756bb
The packag
We need to SRU this into Trusty right?
** Changed in: livecd-rootfs (Ubuntu Trusty)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: livecd-rootfs (Ubuntu Trusty)
Importance
Hello Dan, was your latest commit successful in building a cloud image with a
patched source list?
https://git.launchpad.net/~daniel-thewatkins/ubuntu/+source/livecd-rootfs/commit/?id=1bc0b2eec50726f46510df4a340d2f27f62756bb
--
You received this bug notification because you are a member of Ubunt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title
Ok Dan, let me know if you'd like me to test anything once the build
comes back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security which doe
** Also affects: livecd-rootfs (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security
I still think we should fix this in Ubuntu, just not with the full fix
from the aforementioned bugs. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes tr
Ya! thanks for following up @daniel-thewatkins , I was just about to
message you as I found you helped to resolve another previous docker
image related bug 1645463 with @tianon.
> we should find a less invasive fix.
What would you have in mind. Is there another way we could resolve this
upstream
The fix in bug 1679252 uses LB_PARENT_MIRROR_BINARY_SECURITY for
security lines (where currently trusty uses LB_PARENT_MIRROR_BINARY; I
don't _think_ this should work because LB_PARENT_MIRROR_BINARY is used
for the other sources.list lines which are fine, but it's worth a try.
Commit with that cha
This was fixed for xenial in bug 1513529 and bug 1679252.
(Specifically, the former refactored sources.list generation
significantly and in a way which broke non-x86 architectures, and the
latter remedied that.)
Unfortunately, the changes to sources.list generation were fairly major,
so I don't th
This doesn't exhibit in xenial.
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-securi
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.)
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received t
34 matches
Mail list logo