[Bug 1783225] Re: lxd-client from xenial-backports won't upgrade

[Julian Andres Klode]

Works as designed. APT won't pull in additional backports for an
installed one, unless the additional backports are completely new, as
the release archive has a a higher priority.


** Changed in: apt (Ubuntu)
       Status: New => Invalid

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

Title:
  lxd-client from xenial-backports won't upgrade

Status in apt package in Ubuntu:
  Invalid

Bug description:
  root at malefic:~# apt dist-upgrade; apt-get -o debug::pkgproblemresolver=1 install lxd-client
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
    lxd-client
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) lxd [ amd64 ] < 2.21-0ubuntu3~16.04.2 -> 3.0.1-0ubuntu1~16.04.4 > ( admin )
  Broken lxd:amd64 Depends on liblxc1 [ amd64 ] < 2.0.8-0ubuntu1~16.04.2 | 3.0.1-0ubuntu1~16.04.1 > ( admin ) (>= 3.0.0~)
    Considering liblxc1:amd64 9 as a solution to lxd:amd64 4
      Reinst Failed early because of liblxc1:amd64
    Removing lxd:amd64 rather than change liblxc1:amd64
  Investigating (0) juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel )
  Broken juju-2.0:amd64 Depends on lxd [ amd64 ] < 2.21-0ubuntu3~16.04.2 -> 3.0.1-0ubuntu1~16.04.4 > ( admin )
    Considering lxd:amd64 4 as a solution to juju-2.0:amd64 4
    Removing juju-2.0:amd64 rather than change lxd:amd64
  Investigating (0) python3-juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net )
  Broken python3-juju-deployer:amd64 Depends on juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel )
    Considering juju-2.0:amd64 4 as a solution to python3-juju-deployer:amd64 4
  Broken python3-juju-deployer:amd64 Depends on juju-core [ amd64 ] < none -> 1.25.6-0ubuntu1.16.04.2 > ( universe/devel )
    Considering juju-core:amd64 2 as a solution to python3-juju-deployer:amd64 4
    Try Installing juju-core [ amd64 ] < none -> 1.25.6-0ubuntu1.16.04.2 > ( universe/devel ) before changing python3-juju-deployer:amd64
    Or group remove for python3-juju-deployer:amd64
  Investigating (0) juju [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel )
  Broken juju:amd64 Depends on juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) (>= 1:2.4.0-0ubuntu1~16.04.1~juju1)
    Considering juju-2.0:amd64 4 as a solution to juju:amd64 -1
    Removing juju:amd64 rather than change juju-2.0:amd64
  Investigating (1) juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net )
  Broken juju-deployer:amd64 Depends on python3-juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net )
    Considering python3-juju-deployer:amd64 4 as a solution to juju-deployer:amd64 5
    Added python3-juju-deployer:amd64 to the remove list
    Fixing juju-deployer:amd64 via keep of python3-juju-deployer:amd64
  Done
  The following packages were automatically installed and are no longer required:
    ebtables xdelta3
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    juju-1.25 juju-core
  Suggested packages:
    lxd
  The following packages will be REMOVED
    juju juju-2.0 lxd
  The following NEW packages will be installed
    juju-1.25 juju-core
  The following packages will be upgraded:
    lxd-client
  1 to upgrade, 2 to newly install, 3 to remove and 0 not to upgrade.
  Need to get 39.5 MB of archives.
  After this operation, 54.8 MB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.
  root at malefic:~# 

  Relevant sources.list entry:

  deb http://archive.ubuntu.com/ubuntu/ xenial-backports main restricted
  universe multiverse

  More info: https://paste.ubuntu.com/p/HKnnMcwTyS/

  No apt pinning in play.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1783225/+subscriptions