This bug was fixed in the package juju-quickstart - 1.3.0-0ubuntu1
---
juju-quickstart (1.3.0-0ubuntu1) trusty; urgency=medium
* New upstream release (LP: #1282630).
* Drop patch now included in release: d/p/trusty-jujuclient.
-- Robie BasakWed, 02 Apr 2014 14:02:36 +
**
** Changed in: juju-quickstart (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282630
Title:
[FFe] Upgrade juju-quickstart to new upstream
** Changed in: juju-quickstart (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: juju-quickstart (Ubuntu Trusty)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Yes, we were originally told the feature we were waiting on would be in
release 1.18. It ended up they cut additional releases ahead of 1.18
that implemented what was required. The 1.18 note is no longer valid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
comment #2 makes this bug sound like it requires juju-core 1.18 but
rbasak tells me that's not the case.
FFe approved. In future I'd like some information on QA to have some
assurances that the new features are robust, but it's OK this time.
** Changed in: juju-quickstart (Ubuntu Trusty)
S
** Description changed:
- We just released on PyPi the new 1.2.0 release of quickstart.
+ We just released on PyPi the new 1.3.0 release of quickstart.
Juju core 1.17.2 introduced sudo support for local environments, which
required changes to how quickstart works: calling sudo is now handled by
** Summary changed:
- [FFe] Upgrade juju-quickstart to new upstream release 1.2.0
+ [FFe] Upgrade juju-quickstart to new upstream release 1.3.0
** Description changed:
We just released on PyPi the new 1.2.0 release of quickstart.
Juju core 1.17.2 introduced sudo support for local environment
