I think all we really want to do is make sure we conflict correctly with
the old ppa package names, then dpkg will handle the removal of the old
completion files before starting the install of the new juju-2.0
package.
** Summary changed:
- The tab completion on juju yields KeyError: 'services'
Before we can call this bug complete, the packaging should clean up the
potentially old files that would prevent the bash completion from
working correctly.
I understand we can include a post action that removes the bash
completion files from the old /etc/bash_completion.d/ directory.
Something
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Changed in: juju-core
Importance: High => Critical
** Changed in: juju-core
Importance: Critical => High
--
You received this bug notification because you are a member of
After removing the old files from /etc/bash_completion.d/ I was not able
to get *any* completion to work (in new terminals).
I tried 'juju-2.0 ssh kuber' and that worked, it also started
working to run 'juju ssh kuber'
But it would not work with 'juju ssh kuber' alone until I
symbolically linked
Part of the issue here is having a mix of ppa packages and archive
packages leads to a bunch of bash completion files on disk that may not
correspond to the correct version of juju. We should make our
conflicts/replaces robust on the ppa and archive packages so users can't
have old ppa versions
** Summary changed:
- The tab completion on juju yeilds KeyError: 'services'
+ The tab completion on juju yields KeyError: 'services'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257
Title:
