Warnings? Errors? When updating the whole stack today

[roger peppe]

On 10 June 2013 16:44, John Arbash Meinel <john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2013-06-10 19:03, Roger Peppe wrote:
>> If you try again, it should work. agl has reverted the breaking
>> changes from go.crypto until the release of go1.1.1.
>>
>> We should move to using go1.1.1 when that's released though, unless
>> there's a really compelling reason not to.
>>
> We won't be able to get go 1.1.1 backported to precise, so if we want
> to use the builders to make the juju client binaries that we backport
> to precise, we need to use go 1.0.3.
>
> For binaries on Saucy (and what we upload) we can feel free to use go
> 1.1.1, but we should stay compatible with 1.0.3.

So we can't start using Go 1.1.1 until 2017?

I do hope that's not the case. There are many bugs fixed in 1.1.
We'll also need to make our own forks of external dependencies
such as go.crypto and keep them up to date, which will involve
some resources on our side.