This bug was fixed in the package juju-core -
2.0~beta12-0ubuntu1.16.04.1
---
juju-core (2.0~beta12-0ubuntu1.16.04.1) xenial-proposed; urgency=medium
[ Nicholas Skaggs ]
* New upstream release 2.0-beta12 (LP: #1604137).
* Update debian/copyright.
* Add skip to
Verified I can bootstrap, the gui is pulling the correct version, lxd
and aws all work. Looks good.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Nicholas, or anyone else affected,
Accepted juju-core into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/2.0~beta12-0ubuntu1.16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
** Also affects: juju-core (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Xenial)
Status: New => In Progress
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a
** Changed in: juju-core (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604137
Title:
[SRU] Juju 2.0 beta12 for Xenial
To manage notifications
This bug was fixed in the package juju-core -
2.0~beta12-0ubuntu3.16.10.1
---
juju-core (2.0~beta12-0ubuntu3.16.10.1) yakkety; urgency=medium
* Add skip to current-manual-provider for bug 1605313 and bug 1605050
-- Nicholas Skaggs Thu, 21 Jul 2016
It should be noted we were forced to disable one test as it fails on
some architectures due to https://bugs.launchpad.net/juju-
core/+bug/1605313. As we've released the final tarball for beta12, we'd
like to land this SRU and continue working on squashing that bug
completely in the future.
--