I don't think this is strictly a bug in 'juju-core', more of a bug in the packaging. (Namely saucy has a package named "juju" which is a meta package that installs juju-core, while IIRC python-juju is no longer available on Saucy.)
If this was just 'apt-get upgrade' I would probably agree it shouldn't break things. If it is "apt-get dist-upgrade" then it isn't terrible. The one thing we could consider is that "juju status" with juju-core could notice the environment is python-juju and fail with a nicer error. Unfortunately the new requirement of a certificate means we don't even get far enough to read the bootstrap-verify file in provider storage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200878 Title: Upgrade breaks existing pyjuju deployment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1200878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
