juju-core version 1.11.3 and above will not be compatible with the version of Go in P, Q or R

[David Cheney]

Yup, we're in a rock and a hard place

Here is the state of play

Go 1.0 cannot compile go-curl
Go 1.0.2 can compile go-curl (sorry, this was incorrect before), but
it's TLS library cannot communicate with ec2 reliably
Go 1.1.1 can compile go-curl, but it crashes at runtime, but we can
talk to ec2 properly

Lets decamp to the other thread started by Gavin.

On Wed, Jul 17, 2013 at 8:04 PM, Julian Edwards
<julian.edwards at canonical.com> wrote:
> go-curl is fine on 1.0.2, it's 1.1 that has the problem.
>
> On Wednesday 17 Jul 2013 19:59:26 David Cheney wrote:
>> Go 1.0 (P) and Go 1.0.2 (Q, R) cannot compile the go-curl package
>> which is a dependency of gwacl, which is our Azure provider library.
>> go-curl also request a build time dep on libcurl3-dev, but this is not
>> important at this time.
>>
>> On Wed, Jul 17, 2013 at 7:39 PM, James Page <james.page at ubuntu.com> wrote:
>> > On 17/07/13 04:49, David Cheney wrote:
>> >> There is a problem, Go 1 and Go 1.0.2 in Precise, and Quantal/Raring
>> >> will not be able to build this version from source using the deps that
>> >> are available to the ubuntu builders. This is due to the new
>> >> dependency on a binding to libcurl3-dev.
>> >
>> > I'm not sure I understand; is this a compatibility with golang issue or a
>> > problem with depending on libcurl3-dev?
>> >
>> > --
>> > James Page
>> > Ubuntu Core Developer
>> > Debian Maintainer
>> > james.page at ubuntu.com