[pkg-go] Plans for uploading Go 1.5 to unstable?
Tianon Gravi
admwiggin at gmail.com
Thu Oct 15 19:41:03 UTC 2015
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 <stapelberg at debian.org> wrote:
> Do you have a link with details? I’m curious.
>
> On Thu, Oct 15, 2015 at 7:45 PM, Tianon Gravi <admwiggin at gmail.com> wrote:
>>
>> On 15 October 2015 at 10:40, Michael Stapelberg <stapelberg at debian.org>
>> 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
More information about the Pkg-go-maintainers
mailing list