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

2018-08-22 Thread 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

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

2018-07-24 Thread Stéphane Graber
Ok, so good that this appears to unstick things. Tentatively re- assigning to apt as this feels like a resolver problem. I looked through the debug output again and it's really not obvious why apt came to the conclusion that it'd be preferable to switch from juju2 to juju1 over just upgrading lxd

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

2018-07-24 Thread James Troup
-t xenial-backports works: root@malefic:~# 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: python3-lxc Use 'apt autoremove'

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

2018-07-23 Thread Stéphane Graber
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

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

2018-07-23 Thread Stéphane Graber
If that approach doesn't work, the next try would probably be to specify exact version matches for all those packages to take another part of the APT upgrade calculation out of the equation... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to