juju-core 1.20.11 is not packaged in Ubuntu

[Robie Basak]

juju-core 1.20.11 is proposed for release upstream.

We're now in a position to have this enter trusty-proposed and vivid-proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published 1.20.11 tools in their stable simplestream and announces the release for general production use.

[SRU Information]

juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.

[Development Fix]

Full backport of new upstream release. racb will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.

[Stable Fix]

Full backport of new upstream release.

[Pre-QA tasks]

[racb] Upload to the development release (vivid-proposed): DONE
[racb] Upload to the current LTS release (trusty-proposed): DONE

[QA Status]

Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.

[sinzui] Upsteam QA test against Vivid: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE

Manual tests required:

[sinzui] Test juju-quickstart against vivid-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE

The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.

Landscape team QA: DONE

[Robie Basak (racb)]

Uploaded to vivid-proposed and trusty-proposed. Vivid is ready for testing now. Trusty is pending SRU team approval.

[Brian Murray (brian-murray)]

Hello Robie, or anyone else affected,

Accepted juju-core into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju-core/1.20.11-0ubuntu0.14.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!

[Curtis Hovey (sinzui)]

The juju-local package does not appear to have been built and published. the i386 juju-core package was built but is not listed as published.

[Dean Henrichsmeyer (dean)]

We have thoroughly tested this and it looks good. +1

[Robie Basak (racb)]

Thanks Dean! Note quite verification-done yet though - we have a couple of other verifications we need to do first (tracked in bug whiteboard).

[Scott Kitterman (kitterman)]

Interesting "thorough verification" that completes before the package is in the archive.

[Curtis Hovey (sinzui)]

Vivid testing is complete. It is suitable for local development and for deploying to clouds.

Trusty testing is blocked by the missing juju-local package for 14.14. The vivid local package can be forced to install, but it depends on juju-core >= 1.20.11-0ubuntu1, but the trusty backport is 1.20.11-0ubuntu0, one version less. In short apt-cache tells me I cannot install juju-local 1.20.11 from proposed.

i386 juju-core is missing. The certification tests for i386 cannot be attempted.

[Robie Basak (racb)]

Thanks Curtis!

i386 is blocked on Trusty binNEW. I've asked Steve to review this for us, but I'm not sure when he'll be able to get to it.

[Robie Basak (racb)]

i386 now accepted into trusty-proposed. Thanks Steve!

[Curtis Hovey (sinzui)]

Juju QA certifies that the trusty clients are suitable for local development and production cloud deploys.

[Curtis Hovey (sinzui)]

juju-quickstart 1.3.1 + juju-core 1.20.11 in trusty cannot connect to the bootstraped start-server to deploy services.

    18:40:09 WARNING app@connect:300 Retrying: unable to connect to the Juju API server on wss://165.225.151.107:17070: [Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

I have verified that if I upgrade juju-quickstart to 1.5.0+bzr106 from the stable ppa, I could deploy.
I will try other combinations of juju and quickstart to verify the issue is not a user error.
I do not think juju-core 1.20.11 can go into trusty updates

[Curtis Hovey (sinzui)]

I think my test of juju-quickstart + juju-core failed because my env is dirty. I get the same errors on trusty with the packages in release and updates. I will retest with a clean trusty.

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju-core - 1.20.11-0ubuntu1

---------------
juju-core (1.20.11-0ubuntu1) vivid; urgency=medium

  * New upstream bugfix release (LP: #1386144).
  * Build with a version of libgo5 that has the 64k PAGE_SIZE fix
    (LP: #1377325).
 -- Robie Basak <email address hidden> Mon, 27 Oct 2014 15:32:42 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju-core - 1.20.11-0ubuntu0.14.04.1

---------------
juju-core (1.20.11-0ubuntu0.14.04.1) trusty; urgency=medium

  * New upstream release (LP: #1386144).
  * Packaging changes relating to new upstream release:
    - d/control: add build dependency on lsb-release.
    - d/control: new binary package juju-local-kvm for local KVM support
      (new in Juju 1.20).
    - d/copyright: update for Juju 1.20.11.
    - d/rules: adjust paths in upstream source corresponding to upstream
      move from Launchpad to Github.
    - d/README.source: drop; repacking is no longer required.
  * Packaging bugfixes cherry-picked from Vivid:
    - Build with a version of libgo5 that has the 64k PAGE_SIZE fix
      (LP: #1377325).
    - d/control: add dbus dependency to juju-local (LP: #1343301).
    - d/control: depend on lxc-templates as well as lxc, since lxc only
      recommends lxc-templates so it isn't always brought in.
  * Cherry-pick changes from current upstream and Ubuntu development
    release packaging. These aren't all strictly required for Trusty,
    but given extensive production use of upstream's PPAs, this reduces
    regression risk to end users by eliminating differences between this
    Trusty SRU and what is already known to work well, as well as the
    potential for mistakes because diffs exist:
    - d/{rules,control}: generate mongodb dependency dynamically, as the
      specific binary package name required differs on older releases.
    - d/juju-core.bash-completion: drop unused code.
    - d/control: recommend bash-completion.
    - d/control: update other dependencies for Juju 1.20:
      + Bump golang-go build dependency version; this newer version is
        already available on Trusty.
      + Bump minimum version of lxc dependency; this newer version is
        already available on Trusty.
  * d/control: wrap-and-sort.
 -- Robie Basak <email address hidden> Tue, 28 Oct 2014 15:37:51 +0000

[Colin Watson (cjwatson)]

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.