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 <cl...@ubuntu.com> Mon, 18 Jun 2012 14:00:56 -0700 ** Changed in: juju (Ubuntu Precise) Status: Fix Committed => 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/926550 Title: No way to test proposed updates to juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/926550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs