Upgrading minimum Go version?

Michael Hudson-Doyle michael.hudson at canonical.com
Thu Nov 26 23:49:13 UTC 2015


On 27 November 2015 at 09:39, Tim Penhey <tim.penhey at canonical.com> wrote:
> On 27/11/15 08:43, Michael Hudson-Doyle wrote:
>> On 27 November 2015 at 02:24, Martin Packman
>> <martin.packman at canonical.com> wrote:
>>> On 26/11/2015, Andrew Wilkins <andrew.wilkins at canonical.com> wrote:
>>>> Hi (mostly Curtis),
>>>>
>>>> Is there a plan to bump the minimum Go version? Some of our dependencies do
>>>> not build with Go 1.2. The LXD provider only builds with Go 1.3 (I think?),
>>>> and I've got a PR up that updates the azure-sdk-for-go dependency, but it's
>>>> blocked because the newer doesn't build with Go 1.2.
>>
>> Is this something we've done to ourselves or is there a third-party
>> library we're depending on that doesn't work with Go 1.2?
>
> The two main ones I know about are lxd and the new azure go bindings.

By the azure go bindings you mean something Canonical didn't write,
like https://github.com/Azure/azure-sdk-for-go? That sort of thing
sounds like a good argument for the 1.5-in-trusty SRU thing.

> We have worked around other issues in other library code, like some of
> the x/net stuff.

Do you have a nice list of these workarounds? :-)

Cheers,
mwh



More information about the Juju-dev mailing list