FWIW that isn't what you get if you do "apt-get install foo" you always get the latest version of "foo" that has been patched, not the original one that came with Precise.
I don't have a problem with "juju bootstrap" growing a "--version" target (same as apt-get install foo=1.2.3). But I think our policy of giving you the best version we've released that matches is reasonable. John =:-> On Thu, Apr 17, 2014 at 5:29 PM, Aaron Bentley <aaron.bent...@canonical.com>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 14-04-17 08:40 AM, Andrew Wilkins wrote: > >> Okay. It's possible to do what you want too (see below), but I > >> don't think it's sensible to make that the default behaviour. > > I think that using a tested combination of client and agent is the > most sensible default behaviour. We test that client 1.18.0 is > compatible with agent 1.18.0. We don't test that client 1.18.0 is > compatible with 1.18.1, 1.18.2, etc. I don't think that's worth the > resources. > > (We do, however, test to ensure that upgrades work when the client is > upgraded first.) > > >> If you're bootstrapping 1.18.0 and you don't want the machine > >> agent to upgrade to the most recent patch level, you can override > >> that behaviour by adding this to environments.yaml: > > agent-version: 1.18.0 > > > >> Is that a reasonable solution? > > I don't think that is reasonable. > > It is the wrong default. Users should be able to expect that juju > will always behave the same if they don't explicitly upgrade it. > Installing a different agent runs the risk of incompatibility or > changes in behaviour. The default should be a consistent experience. > > It is the wrong configuration method. bootstrap should support a > - --version, like juju-upgrade. In order to specify agent-version, we > would have to rewrite environments.yaml every time our desired version > changed. Since we test both the stable and devel series our target > version changes frequently. We could potentially rewrite it for every > test run. We might lose the comments or formatting in the process of > rewriting. Constantly rewriting environments.yaml is risky and gross. > > Aaron > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJTT9cgAAoJEK84cMOcf+9hRm8H/1l7g+L8ZPWkbXrBEzyvEm52 > cL6CBPz3cYqVzbK1YrihyuiqrVYeJy4Dh4sPJX1dRtpOx0aZHOFx8C/sV7QDx2M0 > EEJyvTRfNGLvq6+rpmEYj5cH0jWjove2a0bTky/dDd/7hFRZWXIeMZLtazQTmnZq > KkLp+60/pQ5Zxo1ojRrtf4mSxEDC+FBst6m+iwvayllOsC62ViPQehPDEApxUMCI > HFRv45ROSpZM+MprjZJOVla3wUajlbNYGHtkfAU45kZsP7Lfm/U5Zbj1wuqVdlGe > JP7gHwKbCBRIakRsxxIyg9theIpqjhZaeYQ99TNYO0dR/INKNXAQzzDFP9Trvm8= > =itpS > -----END PGP SIGNATURE----- > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
