No way to test proposed updates to juju

[Clint Byrum]

[Impact]
Users will not be able to test any proposed updates to juju in deployed nodes.

[Dev Fix]
Add a new origin "proposed" to that environments will enable the proposed pocket on deployed nodes.

[Stable Fix]
Backport of Dev Fix

[Test Case]
1. edit ~/.juju/environments.yaml and set 'origin: proposed' on an environment
2. bootstrap said environment (juju bootstrap -e envname)
3. Verify that bootstrap node has proposed pocket enabled using 'juju ssh 0'. If there are proposed juju updates for that release, verify that juju was installed from proposed.

[Regression Potential]
Very Low. The fix just adds a new origin type, 'proposed', so the others are not really affected and the logic leading to all of the origin types is very straightforward. There is also very good test coverage of the affected code.

== Original Bug Description ==

juju-origin in environments.yaml needs to accept 'distro-proposed', or environments.yaml needs to accept some other option that will allow directing juju to install the version of juju from the -proposed pocket.

The simplest thing is to allow juju-origin to have the URL of a .deb.

This is currently blocking the ability to do an SRU for the bugs fixed in juju since the Ubuntu 11.10 release.

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju - 0.5+bzr538-0ubuntu1

---------------
juju (0.5+bzr538-0ubuntu1) quantal; urgency=low

  * New upstream snapshot (LP: #993034, LP: #926550)
 -- Clint Byrum <email address hidden> Tue, 29 May 2012 22:36:40 -0700

[Chris Halse Rogers (raof)]

Hello Clint, or anyone else affected,

Accepted juju into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Clint Byrum (clint-fewbar)]

After bootstrapping with the version of juju in proposed, and setting 'juju-origin: proposed', my bootstrap node started up, with this:

juju:
  Installed: 0.5+bzr531-0ubuntu1.1
  Candidate: 0.5+bzr531-0ubuntu1.1
  Version table:
 *** 0.5+bzr531-0ubuntu1.1 0
        500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ precise-proposed/universe amd64 Packages
        100 /var/lib/dpkg/status
     0.5+bzr531-0ubuntu1 0
        500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

Verified.

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju - 0.5+bzr531-0ubuntu1.2

---------------
juju (0.5+bzr531-0ubuntu1.2) precise-proposed; urgency=low

  * d/p/upstream-541-542.patch: fix shell script to make proposed work
    for local provider. (LP: #1007657)

juju (0.5+bzr531-0ubuntu1.1) precise-proposed; urgency=low

  * d/p/upstream-532.patch: use proper whitespace separation in
    relation-ids. (LP: #988065)
  * d/p/upstream-533.patch: workaround to suppress Zookeeper logging
    which goes out of control in local provider on Reboot.(LP: #958312)
  * d/p/upstream-534.patch: fix to stop juju-log and relation-set commands
    outputting "{}" to stdout, which can break some programs and makes it
    difficult to use them in a debug-hooks session. (LP: #915506)
  * d/p/upstream-537.patch: make HTTPS apt sources usable inside local
    provider. (LP: #993034)
  * d/p/upstream-538.patch: Add support to install juju from proposed
    pocket to test proposed SRU's. (LP: #926550)
 -- Clint Byrum <email address hidden> Mon, 18 Jun 2012 14:00:56 -0700

[Rolf Leggewie (r0lf)]

oneiric has seen the end of its life and is no longer receiving any updates. Marking the oneiric task for this ticket as "Won't Fix".