Comment 2 for bug 1633593

This issue should have no effect on 1.25 deployments. Users will have to run update-alternatives after upgrading no matter what. Running it now results in restoring juju-1.25, which is the desired outcome. After a new package for 2.0 is uploaded that supports using update-alternatives (and thus this bug is fixed), it will allow you to easily toggle between them as expected. That will be the only change from the current setup.