Does this mean we can assume 1.6 for everything from now on, or is there some other step we're waiting on? I have some code that only needs to exist while we support 1.2, and I'd be happy to just delete it.
On Thu, Mar 24, 2016, 4:07 AM Tim Penhey <tim.pen...@canonical.com> wrote: > Awesome news Michael. > > Thank you for all your work on this. > > Tim > > On 24/03/16 19:03, Michael Hudson-Doyle wrote: > > Hi, > > > > As of a few minutes ago, there is now a golang-1.6 package in > > trusty-proposed: > > https://launchpad.net/ubuntu/trusty/+source/golang-1.6 (thanks for the > > review and copy, Steve). > > > > One difference between this and the package I prepared earlier is that > > it does not install /usr/bin/go but rather /usr/lib/go-1.6/bin/go so > > Makefiles and such will need to be adjusted to invoke that directly or > > put /usr/lib/go-1.6/bin on $PATH or whatever. (This also means it can > > be installed alongside the golang packages that are already in > > trusty). > > > > Cheers, > > mwh > > (Hoping that we can now really properly ignore gccgo-4.9 ppc64el bugs!) > > > > On 17 February 2016 at 07:58, Michael Hudson-Doyle > > <michael.hud...@canonical.com> wrote: > >> I have approval for the idea but also decided to wait for 1.6 and upload > >> that instead. I'm also on leave currently so hopefully this can all > happen > >> in early March. > >> > >> Cheers, > >> mwh > >> > >> On 17/02/2016 1:17 am, "John Meinel" <j...@arbash-meinel.com> wrote: > >>> > >>> To start with, thanks for working on this. However, doesn't this also > >>> require changing the CI builds to use your ppa? > >>> > >>> What is the current state of this? I was just looking around and > noticed > >>> golang1.5-go isn't in anything specific for Trusty that I can see. I > realize > >>> if its going into an SRU it requires a fair amount of negotiation with > other > >>> teams, so I'm not surprised to see it take a while. I just wanted to > check > >>> how it was going. > >>> > >>> Thanks, > >>> > >>> John > >>> =:-> > >>> > >>> On Mon, Jan 18, 2016 at 7:32 AM, Michael Hudson-Doyle > >>> <michael.hud...@canonical.com> wrote: > >>>> > >>>> Hi all, > >>>> > >>>> As part of the plan for getting Go 1.5 into trusty (see here > >>>> https://wiki.ubuntu.com/MichaelHudsonDoyle/Go15InTrusty) I've built > >>>> packages (called golang1.5-go rather than golang-go) for trusty in my > >>>> ppa: > >>>> > >>>> https://launchpad.net/~mwhudson/+archive/ubuntu/go15-trusty/+packages > >>>> > >>>> (assuming 3:1.5.3-0ubuntu4 actually builds... I seem to be having a > >>>> "make stupid packaging mistakes" day) > >>>> > >>>> I'll write up a SRU bug to start the process of getting this into > >>>> trusty tomorrow but before it does end up in trusty it would seem like > >>>> a good idea to run the CI tests using juju-core packages built with > >>>> this version of the go compiler. Is that something that's feasible to > >>>> arrange > >>>> > >>>> The only packaging requirement should be to change the build-depends > >>>> to be on golang1.5-go rather than golang-go or gccgo. > >>>> > >>>> Cheers, > >>>> mwh > >>>> > >>>> -- > >>>> Juju-dev mailing list > >>>> Juju-dev@lists.ubuntu.com > >>>> Modify settings or unsubscribe at: > >>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev > >>> > >>> > >> > > > > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
