This is pretty weird and I'm wondering if this is an apt bug rather than
a lxd packaging bug...

I tried to reproduce your environment here by installing the packages
that were conflicting on your system, then doing the LXD upgrade from
stock xenial over to backports:

```
root@backports:~# dpkg -l | grep juju
ii  juju                                2.3.7-0ubuntu0.16.04.1                  
   all          next generation service orchestration system
ii  juju-2.0                            2.3.7-0ubuntu0.16.04.1                  
   amd64        Juju is devops distilled - client
ii  juju-deployer                       0.6.4-0ubuntu1                          
   all          Deploy complex stacks of services using Juju
ii  python-jujuclient                   0.50.5-0ubuntu2~16.04                   
   all          Python API client for Juju (Python 2)
root@backports:~# dpkg -l | grep lxd
ii  lxd                                 2.0.11-0ubuntu1~16.04.4                 
   amd64        Container hypervisor based on LXC - daemon
ii  lxd-client                          2.0.11-0ubuntu1~16.04.4                 
   amd64        Container hypervisor based on LXC - client
root@backports:~# apt install -t xenial-backports lxd lxd-client
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  ebtables liblxc-common liblxc1 lxcfs xdelta3
Suggested packages:
  criu lxd-tools
The following packages will be REMOVED:
  lxc-common
The following NEW packages will be installed:
  ebtables liblxc-common xdelta3
The following packages will be upgraded:
  liblxc1 lxcfs lxd lxd-client
4 upgraded, 3 newly installed, 1 to remove and 0 not upgraded.
Need to get 8571 kB of archives.
After this operation, 5795 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-backports/main amd64 liblxc1 
amd64 3.0.1-0ubuntu1~16.04.1 [235 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-backports/main amd64 
liblxc-common amd64 3.0.1-0ubuntu1~16.04.1 [77.9 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 ebtables 
amd64 2.0.10.4-3.4ubuntu2.16.04.2 [79.9 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports/main amd64 lxcfs 
amd64 3.0.1-0ubuntu2~16.04.1 [38.7 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-backports/main amd64 lxd amd64 
3.0.1-0ubuntu1~16.04.4 [5178 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-backports/main amd64 
lxd-client amd64 3.0.1-0ubuntu1~16.04.4 [2894 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 xdelta3 amd64 
3.0.8-dfsg-1ubuntu2 [67.1 kB]
Fetched 8571 kB in 0s (17.2 MB/s)  
(Reading database ... 27770 files and directories currently installed.)
Preparing to unpack .../liblxc1_3.0.1-0ubuntu1~16.04.1_amd64.deb ...
Unpacking liblxc1 (3.0.1-0ubuntu1~16.04.1) over (2.0.8-0ubuntu1~16.04.2) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
(Reading database ... 27770 files and directories currently installed.)
Removing lxc-common (2.0.8-0ubuntu1~16.04.2) ...
Selecting previously unselected package liblxc-common.
(Reading database ... 27749 files and directories currently installed.)
Preparing to unpack .../liblxc-common_3.0.1-0ubuntu1~16.04.1_amd64.deb ...
Unpacking liblxc-common (3.0.1-0ubuntu1~16.04.1) ...
Selecting previously unselected package ebtables.
Preparing to unpack .../ebtables_2.0.10.4-3.4ubuntu2.16.04.2_amd64.deb ...
Unpacking ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
Preparing to unpack .../lxcfs_3.0.1-0ubuntu2~16.04.1_amd64.deb ...
Unpacking lxcfs (3.0.1-0ubuntu2~16.04.1) over (2.0.8-0ubuntu1~16.04.2) ...
Preparing to unpack .../lxd_3.0.1-0ubuntu1~16.04.4_amd64.deb ...
Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
Unpacking lxd (3.0.1-0ubuntu1~16.04.4) over (2.0.11-0ubuntu1~16.04.4) ...
Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
Preparing to unpack .../lxd-client_3.0.1-0ubuntu1~16.04.4_amd64.deb ...
Unpacking lxd-client (3.0.1-0ubuntu1~16.04.4) over (2.0.11-0ubuntu1~16.04.4) ...
Selecting previously unselected package xdelta3.
Preparing to unpack .../xdelta3_3.0.8-dfsg-1ubuntu2_amd64.deb ...
Unpacking xdelta3 (3.0.8-dfsg-1ubuntu2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Setting up lxcfs (3.0.1-0ubuntu2~16.04.1) ...
Setting up lxd-client (3.0.1-0ubuntu1~16.04.4) ...
Setting up xdelta3 (3.0.8-dfsg-1ubuntu2) ...
Setting up liblxc1 (3.0.1-0ubuntu1~16.04.1) ...
Setting up liblxc-common (3.0.1-0ubuntu1~16.04.1) ...
Installing new version of config file 
/etc/apparmor.d/abstractions/lxc/container-base ...
Installing new version of config file 
/etc/apparmor.d/abstractions/lxc/start-container ...
Setting up lxd (3.0.1-0ubuntu1~16.04.4) ...
Installing new version of config file /etc/init.d/lxd ...
Removing obsolete conffile /etc/init/lxd.conf ...
Setting up lxd dnsmasq configuration.

Old bridge configuration detected in /etc/default/lxd-bridge, upgrading
Unsetting deprecated profile options
Attempting to kill current lxd-bridge
Stock LXD installation detected, resetting to new defaults
Cleaning up lxd-bridge state files

Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
root@backports:~# 
```

I wonder if it's the lxc-common replacement by liblxc-common that's
somehow causing issues on your system. Could you maybe try something
like this:


    apt install -t xenial-backports lxd lxd-client liblxc1 lxcfs liblxc-common

I wonder if that'll make APT realize that it can totally solve that
upgrade by just pulling in the bits that LXD needs and that those do
satisfy the dependencies of the existing packages.

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to