[Bug 1679252] Re: Cloud images for non-Intel architectures are configured with security repos that don't work

[Edward Vielmetti]

Is anyone testing armhf?

I ask because of this from @andrewhsu at Docker, at
https://github.com/docker/docker/issues/32335#issuecomment-292042111

> This issue is preventing the release of docker 17.04.0 for ubuntu
xenial on armhf. Ubuntu xenial on amd64 is fine, however, so packages
are available for that. When the armhf/ubuntu:xenial image is fixed, the
corresponding 17.04.0 packages will be built and released.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1679252

Title:
  Cloud images for non-Intel architectures are configured with security
  repos that don't work

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Users who don't get a fresh sources.list written out on first boot
  (e.g. Docker users) can't install updates from xenial-security on non-
  Intel architectures.

  [Test Case]

  Run an ubuntu-cpc livefs build for a non-Intel architecture, unpack
  one of the produced root tarballs, chroot in to it and perform an
  `apt-get update`.  You should see no errors.

  [Regression Potential]

  This change modifies the sources that apt will use for updates, so the
  biggest risk for regression is that the fix is malformed and systems
  become un-updateable (either partially or fully).  The test above
  should catch this.

  [Original Report]

  In the fix for bug 1513529, we[0] modified livecd-rootfs to write out
  a sources.list that matches the sources.list in Ubuntu Server
  installed from an ISO.  We (presumably) compared to an Intel
  installation, and hard-coded security.ubuntu.com as a repo in
  sources.list.

  Unfortunately, packages for non-Intel architectures aren't published
  to security.ubuntu.com; they are instead published at
  http://ports.ubuntu.com/ubuntu-ports/.  That should be the URL that we
  configure as the source for $SUITE-security.

  [0] Well, *ahem*, _I_.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1679252/+subscriptions