[Bug 2123595] [NEW] ISO builds pull packages from {ports, archive}.ubuntu.com

[Michael Hudson-Doyle]

Public bug reported:

The intent (or so I always thought anyway) is that all packages
installed during livefs use an "building" apt config which refers to
ftpmaster.internal, even though our images obviously ship with an
"shipped" config which references whichever of
{ports,archive}.ubuntu.com make sense. But there is evidence that they
don't, for example when ports and ftpmaster were out of sync, builds
failed in ways that made no sense when looking at the state of the
archive from the Launchpad side.

Another reason this is bad is that for Ubuntu builds the only components
configured for the "building" config are main and restricted but all
components are enabled in the "shipped" config. If we install packages
with the shipped config active, we can include universe packages by
mistake.

Given the way layered builds have to swap between configs to make all
this work, I'm not surprised that it isn't quite right. But well, we
should try to fix it!

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/2123595

Title:
  ISO builds pull packages from {ports,archive}.ubuntu.com

Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  The intent (or so I always thought anyway) is that all packages
  installed during livefs use an "building" apt config which refers to
  ftpmaster.internal, even though our images obviously ship with an
  "shipped" config which references whichever of
  {ports,archive}.ubuntu.com make sense. But there is evidence that they
  don't, for example when ports and ftpmaster were out of sync, builds
  failed in ways that made no sense when looking at the state of the
  archive from the Launchpad side.

  Another reason this is bad is that for Ubuntu builds the only
  components configured for the "building" config are main and
  restricted but all components are enabled in the "shipped" config. If
  we install packages with the shipped config active, we can include
  universe packages by mistake.

  Given the way layered builds have to swap between configs to make all
  this work, I'm not surprised that it isn't quite right. But well, we
  should try to fix it!

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