So, the workaround is manually delete the /etc/bash_completion.d/juju-core file - but that's something the 2.0 packaging really does need to do in a post-install step or similar.
So, the workaround is manually delete the /etc/bash_ completion. d/juju- core file - but that's something the 2.0 packaging really does need to do in a post-install step or similar.