Public bug reported:
juju-core is expected to land a change that will break juju-quickstart.
We can fix this in the archive today, but if this happens after Trusty's
release, we'll be stuck.
This demonstrates a wider problem here, which is that this is a
consequence of juju-quickstart installing Juju from its PPA by default.
After discussion with the juju-quickstart team, the conclusion is that
juju-quickstart as installed from the archive should do --distro-only
behaviour by default (ie. not enable any PPAs by default), even if it
does make sense for it to use the PPA by default when installed from
other sources (eg. PPA and PyPI). Then, juju-quickstart as installed
from the archive will only ever use juju-core from the archive.
We have agreed that juju-quickstart will have an option that is the
opposite of --distro-only (eg. --ppa), which will be the default
upstream, but we will distro-patch the default the other way round in
the archive to resolve this issue.
** Affects: juju-quickstart (Ubuntu)
Importance: High
Status: Triaged
** Affects: juju-quickstart (Ubuntu Trusty)
Importance: High
Status: Triaged
** Also affects: juju-quickstart (Ubuntu Trusty)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1301481
Title:
juju-quickstart will be broken in Trusty after juju-core updates in
its stable PPA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1301481/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
