On Fri, Nov 27, 2015 at 7:49 AM Michael Hudson-Doyle < [email protected]> wrote:
> On 27 November 2015 at 09:39, Tim Penhey <[email protected]> wrote: > > On 27/11/15 08:43, Michael Hudson-Doyle wrote: > >> On 27 November 2015 at 02:24, Martin Packman > >> <[email protected]> wrote: > >>> On 26/11/2015, Andrew Wilkins <[email protected]> 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. > Yes, that's the one. They depend on, and are vendoring, a version of go.crypto that doesn't build with Go 1.2. > 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 > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
