This bug was fixed in the package juju-core - 2.0~beta7-0ubuntu1.16.04.1
---
juju-core (2.0~beta7-0ubuntu1.16.04.1) xenial-proposed; urgency=medium
* New upstream release 2.0-beta7 (LP: #1581645)
-- Nicholas Skaggs Fri, 13 May 2016
15:22:03 -0400
I have installed the proposed package on trusty and verified its
functionality.
** 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~beta7-0ubuntu1.16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a
** Changed in: juju-core (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581645
Title:
[SRU] Juju 2.0 beta7 for Xenial
To manage notifications about this
** Also affects: juju-core (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581645
Title:
[SRU] Juju 2.0 beta7 for Xenial
To manage