I am pretty sure that @pangkit's status changes were invalid. I'll
revert them back to what they were prior to these changes.
** Changed in: juju
Status: In Progress => Invalid
** Changed in: juju-core (Ubuntu)
Status: In Progress => Invalid
** Changed in: juju-release-tools
** Changed in: juju-release-tools
Status: Fix Committed => Confirmed
** Changed in: juju-release-tools
Status: Confirmed => Fix Committed
** Changed in: juju-release-tools
Status: Fix Committed => In Progress
** Changed in: juju
Status: Invalid => In Progress
**
** Changed in: juju-release-tools
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613864
Title:
Missing "juju-2"/"juju2" command.
To manage notifications about this
This issue should be corrected now as of 2.1-beta5. There is a juju-2
symlink you can depend on that will point to the latest juju-2 binary on
your system.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
** Changed in: juju
Status: Triaged => Invalid
** Changed in:
Removing 2.1 milestone as we will not be addressing this issue in 2.1.
** Changed in: juju
Milestone: 2.1.0 => None
** Tags added: usability
** Also affects: juju-release-tools
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Project changed: juju-core => juju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613864
Title:
Missing "juju-2"/"juju2" command.
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613864
Title:
Ideally we don't have that many aliases for the same thing (and some of
those /usr/bin files are not from our latest packaging)?
I think what you really want is to just run `/usr/bin/juju` but realise
having juju-1-default makes that more complicated as well. So, I see
some benefit in a
