-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 That may be true, but the LXD provider branch has a stale version number. Once the version number is updated to 1.26-alpha2, I imagine the lxd provider will no longer try to use the released streams.
The stale version number is also causing builds to fail: http://reports.vapour.ws/releases/3272 http://reports.vapour.ws/releases/3277 On 2015-11-06 10:18 AM, Eric Snow wrote: > If you are using the LXD provider, built from the lxd-provider > feature branch, then make sure you use the --upload-tools option > when bootstrapping. > > Since the 1.26-alpha1 stream has been released, Juju will download > that instead of the juju you built from the lxd-provider feature > branch. That means that the machine agent on new instances (e.g. > the new controller) will not know about the LXD provider. Note > that this is the same as any other provider. Just a heads up. :) > > -eric > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWPMogAAoJEK84cMOcf+9h96AIAL7K/ZORFnApxE501biVAyG4 NYZvl0E8JR+pXU8e0Zl/WUSuxwyxfFRczgrg1+WFSVUDcZmuMSIQdtG9O+zvc4lH QIe5aBKbRTdYy3s3HQo4wXTYZ5osaGQhdp2tSdEnEJpoWSKFMvLHoX+SJaxV0BfY OfspXLiHR4g9iQb7A+6bvnl1hoq5051iMgLreAq0AVMT1NfDioZNDjTMY19HvMm2 GNcOdhW3lrliUUZvpdVx1FCqBO5e5FR1BfozzoAchCjv16o/EdVyrIxfcF3D9HVQ VbTf2DJmKp/n6Ed/cL8swQ8wXRWwrBeHkk3LpxnFh/ZLD6eDCYr1+TIpMGLI5mE= =mQEb -----END PGP SIGNATURE----- -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
