Ok this may actually be a testing issue. We are aledgedly testing the
"current" version of lxc against a specific kernel version:
adt-run [11:23:50]: host juju-prod-ues-proposed-migration-machine-5;
command line: /home/ubuntu/autopkgtest/runner/adt-run --output-dir /tmp
/adt-run.out.yaBjME
This appears to be an infrastructure issue, handing off to testing.
** Also affects: auto-package-testing
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Indeed this is fallout from bug 1177432, where cloud-init changed to add
-backports (even on stables).
** Changed in: auto-package-testing
Importance: Undecided => Critical
** Changed in: auto-package-testing
Status: New => In Progress
** Changed in: auto-package-testing
This appears to be related to the changes applied to the cloud images
under bug: #1177432.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1517426
Title:
[trusty] lxc: lxc now depends
I mitigated this by adding this beauty to the worker.conf's setup
commands:
sed -i '/^deb.*-backports/d' /etc/apt/sources.list `ls
/etc/apt/sources.list.d/*2>/dev/null || true`
A more elegant fix would be to tell apt-get source to somehow respect
the apt pinning, i. e. get the source from
