-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> 4) IIRC we use the version of the juju client when we upload, not >> the version of the jujud binary. Eg if you happen to have a 1.22 >> jujud on your system but you use a 1.23-beta2 client we'll >> upload it but call it 1.23.0.1-beta2. From there upgrades etc >> will be very confused. > > I suspect this is true. A development client can make surprising > decisions when upgrading a stable environment. >
It is true because --upload-tools forces the built tarball to *lie* about its actual version. So even though you might actually have 1.20.x binaries inside the tarball (e.g. left in your $PATH from before) --upload-tool prepares, it will *appear* as they are x.y.z.1, where x.y.z is your juju client's version (or when you have the source - - the value of Current in version/version.go). Beware. - -- Dimiter Naydenov <[email protected]> juju-core team -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUt9dVAAoJENzxV2TbLzHwjNUIAJQXyDeQCywDp4vCKLquTSLF ZAY/Z6GJ/yF0ptYyiECVPuBjnzIQXMKxXfPYAQmFBTyWeb+mOljnGS8oGr3Nem7N lIGuPHGUU0VNJLVRau+JjxTp89BEUR5eNKtQnmzPlU2ZyceSx5DuPnQ4H/uvmJsj Xrb/KzVpwNn5K4hlw+d0ZPzZOA0hCKUXJYK04gUT6+rnYiQP2Ek8ywxrbGs6sQ9J LznQ1ZxwlIcgF2Y0e6WycomiR52lOBL/LK8/IL4OHCXlIYai34LTLUDU2uH8CRF0 v6zYxyPuvsKZ/pLxPtTxxYs8HB7nOHZawQ7pI+qO94KS7fDi+O0ntFR66n8k4YY= =h2in -----END PGP SIGNATURE----- -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
