Sadly, being stuck in -proposed is probably correct for beta3, due to the above mentioned lxd breakages.
Note that the future-lxd-provider gets futher, but still breaks due to changes in lxd since the test was last modified with beta2: + lxd-images import ubuntu yenial --alias ubuntu-yenial debian/tests/lxd-provider: line 8: lxd-images: command not found Also, we don't have coverage for lxd on armhf or s390x as they can't provide machine-level isolation. That's probably fine, but can maybe be improved when we have more confidence lxd/juju won't blow things up as much as the dev versions have tended to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
