lxc / lxc1 uninstallable

[Hadmut Danisch]

Hi,

I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc during upgrade, because the upgrade process removed it.

Now I can't install lxc due to broken dependencies/incomplete package upload:

 lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed

 lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed
        Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed
        Recommends: libpam-cgfs but it is not going to be installed
        Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed

liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1).

python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed

Obviously someone has rendered lxc uninstallable by putting an incomplete set of packages in the 16.04 repository.

Please fix.

[Hadmut Danisch (hadmut)]

Strange side effect:

Launchpad didn't let me report the bug against the package lxc1 because launchpad insists that there is no lxc1 package.

[Stéphane Graber (stgraber)]

The reason why your upgrade broke is because you were using the LXC PPA on 14.04 which effectively meant you had a more recent version of LXC than is in 16.04.

You should be able to fix things by either removing all those packages and reinstalling them clean from the 16.04 archive, or by re-enabling the PPA, this time for 16.04, which should also fix the issue.

In either case, upgrading systems with PPAs is effectively an unsupported use case, and as annoying as it is in this case, APT is right to refuse this "upgrade" as it mixes packages that were meant for 14.04 with some that were meant for 16.04...

[Stéphane Graber (stgraber)]

As for Launchpad, bug reports are tied to source package name, instead of binary package name, so the "lxc" package is correct.