[SRU] Juju 2.0 beta12 for Xenial

[Nicholas Skaggs]

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 stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates.

[Impact]
This update brings many critical fixes and enhancements in comparison to the current beta7 release. We've been careful in choosing the next release for xenial with the mindset of keeping things current and stable.

A full list of targeted bugs can be seen against the milestone, and the intervening milestones:

https://launchpad.net/juju-core/+milestone/2.0-beta12
https://launchpad.net/juju-core/+milestone/2.0-beta11
https://launchpad.net/juju-core/+milestone/2.0-beta10
https://launchpad.net/juju-core/+milestone/2.0-beta9
https://launchpad.net/juju-core/+milestone/2.0-beta8

[QA/Testing]
Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here.

http://reports.vapour.ws/releases/4141

In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/.

Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates

[Nicholas Skaggs (nskaggs)]

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.

[Launchpad Janitor (janitor)]

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 <email address hidden> Thu, 21 Jul 2016 15:12:52 -0400

[Chris J Arges (arges)]

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 package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Nicholas Skaggs (nskaggs)]

Verified I can bootstrap, the gui is pulling the correct version, lxd and aws all work. Looks good.

[Launchpad Janitor (janitor)]

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 current-manual-provider for bug 1605313 and bug 1605050
  * Fix adt test for manual-provider

  [ Martin Packman ]
  * Allow stripping of go binaries (LP: #1564662).
  * Mark juju-2.0 as conflicting and replacing old ppas (LP: #1600257).
  * Adjust where bash completion script is installed (LP: #1588403).

 -- Nicholas Skaggs <email address hidden> Mon, 18 Jul 2016 14:00:19 -0400

[Chris J Arges (arges)]

The verification of the Stable Release Update for juju-core has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.