Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Michael Hudson-Doyle]

If you're impatient, I'm pretty sure recent enough docker builds with
gccgo on arm64.

On 14 October 2015 at 12:43, Potter, Tim (Converged Cloud)
 wrote:
> Hi tianon.  I was curious what your plans were for uploading Go 1.5 to 
> unstable.  Is there anything you can share?
>
> I’m pretty keen on seeing Docker running on arm64 which should get pulled in 
> as golang-go is a B-D.
>
>
> Thanks,
>
> Tim.
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Michael Hudson-Doyle]

On 16 October 2015 at 06:40, Michael Stapelberg  wrote:
>
>
> On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi  wrote:
>>
>> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud)
>>  wrote:
>> > Hi tianon.  I was curious what your plans were for uploading Go 1.5 to
>> > unstable.  Is there anything you can share?
>>
>> Go 1.5 has some minor breaking changes, so I've been waiting until I
>> (or some other kind soul) has had the time to do a full ratt run on Go
>> 1.5 and make sure all our packages either build/test successfully or
>> that we have a plan/patches ready to fix the issues that are bound to
>> come up.
>
>
> FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
> its Go 1 stability guarantee, and any package which breaks likely did
> something wrong in the first place :). If this is the only thing that’s
> holding back the upload, I’d recommend to just go ahead with the upload.

That's a nice idea, and for pure go things it might even be close to
true, but it's definitely not true universally. Here's a few reasons
for failures I saw when prepping 1.5 for ubuntu:

1) cgo is a particularly rich source of incompatibilities (see docker,
and also the tightening over time rules about passing Go pointers to
C)
2) the go tool now explodes if you're careless and set GOPATH to have
an empty component
3) packages that have expectations of what tracebacks look like in
their testsuite
4) testing/quick can produce nil pointers now
5) golang-x-text was broken by a new unicode version
6) a few ftbfs on arm builders with low ram

Some of these are definitely bugs in the package or packaging but not all.

Cheers,
mwh

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Tianon Gravi]

Sure! :)  On the Docker end, the discussion is in
https://github.com/docker/docker/pull/15703 (and you're correct that
it's Docker doing something "wrong", but isn't it still worth checking
so we don't get random FTBFS?  or do we just not worry about it and do
something about them as they come?)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


On 15 October 2015 at 11:08, Michael Stapelberg  wrote:
> Do you have a link with details? I’m curious.
>
> On Thu, Oct 15, 2015 at 7:45 PM, Tianon Gravi  wrote:
>>
>> On 15 October 2015 at 10:40, Michael Stapelberg 
>> wrote:
>> > FWIW, I don’t think that’s necessary for the compiler itself. Go adheres
>> > to
>> > its Go 1 stability guarantee, and any package which breaks likely did
>> > something wrong in the first place :). If this is the only thing that’s
>> > holding back the upload, I’d recommend to just go ahead with the upload.
>>
>> Right, in theory, that's supposed to be the case.  I've seen several
>> examples already where that's not the case, including Docker itself.
>>
>> ♥,
>> - Tianon
>>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>
>
>
>
> --
> Best regards,
> Michael

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Tianon Gravi]

On 15 October 2015 at 10:40, Michael Stapelberg  wrote:
> FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
> its Go 1 stability guarantee, and any package which breaks likely did
> something wrong in the first place :). If this is the only thing that’s
> holding back the upload, I’d recommend to just go ahead with the upload.

Right, in theory, that's supposed to be the case.  I've seen several
examples already where that's not the case, including Docker itself.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Michael Stapelberg]

On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi  wrote:

> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud)
>  wrote:
> > Hi tianon.  I was curious what your plans were for uploading Go 1.5 to
> unstable.  Is there anything you can share?
>
> Go 1.5 has some minor breaking changes, so I've been waiting until I
> (or some other kind soul) has had the time to do a full ratt run on Go
> 1.5 and make sure all our packages either build/test successfully or
> that we have a plan/patches ready to fix the issues that are bound to
> come up.
>

FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
its Go 1 stability guarantee, and any package which breaks likely did
something wrong in the first place :). If this is the only thing that’s
holding back the upload, I’d recommend to just go ahead with the upload.


>
> To Michael's point about compiling Docker via gccgo -- as the
> maintainer of the build scripts for upstream, please don't do that for
> anything serious.  I've been working closely with IBM on that, and
> none of us are really thrilled with the results so far, but it's the
> only way we can get anything at all on some of their more interesting
> architectures like s390x.
>
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

[pkg-go] Plans for uploading Go 1.5 to unstable?

[Potter, Tim (Converged Cloud)]

Hi tianon.  I was curious what your plans were for uploading Go 1.5 to 
unstable.  Is there anything you can share?

I’m pretty keen on seeing Docker running on arm64 which should get pulled in as 
golang-go is a B-D.


Thanks,

Tim.
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers