[Bug 1754657] Re: [SRU] python-pylxd 2.0.7 (xenial), python-pylxd 2.2.6 (artful)

[Alex Kavanagh]

@coreycb pike-proposed on xenial is giving python 2.2.6, which is fine
as it will work. 2.0.7 is in xenial standard:

sudo add-apt-repository cloud-archive:pike-proposed
sudo apt update
sudo apt install python-pylxd
apt policy python-pylxd

python-pylxd:
  Installed: 2.2.6-0ubuntu0.17.10.1~cloud0
  Candidate: 2.2.6-0ubuntu0.17.10.1~cloud0
  Version table:
 *** 2.2.6-0ubuntu0.17.10.1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-proposed/pike/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.7-0ubuntu1 500
        500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
     2.0.0-0ubuntu1 500
        500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

This will certainly work as a combination of xenial/nova-lxd/pylxd and further testing demonstrates that.
Happy to close.

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

Title:
  [SRU] python-pylxd 2.0.7 (xenial), python-pylxd 2.2.6 (artful)

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in python-pylxd package in Ubuntu:
  Invalid
Status in python-pylxd source package in Xenial:
  Fix Released
Status in python-pylxd source package in Artful:
  Won't Fix

Bug description:
  [Impact]
  This SRU gets us to the latest pylxd point releases for xenial and artful.

  [Test Case]
  Upstream integration tests will be run against the python-pylxd installed from -proposed: https://github.com/lxc/pylxd/blob/master/run_integration_tests

  Instead of running 'tox -e integration' run 'nosetests integration'.

  [Regresion Potential]
  Regression potential is minimal. This is an upstream patch version update to the same major/minor 2.0.x version that is already in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1754657/+subscriptions