On Mon, 15 Apr 2019, Thomas Goirand wrote:
> On 4/15/19 9:24 AM, Hideki Yamane wrote:
> > On Sun, 14 Apr 2019 21:11:09 +0200
> > "Dr. Tobias Quathamer" wrote:
> >> I think it's the right decision of the release team to stick with golang
> >> 1.11 for buster. The previous migration from golang
On 4/14/19 1:00 PM, Toni Mueller wrote:
> Or how about removing Python2 altogether, then?
That's actually not a bad idea, which we considered, and only postponed
until Buster is out. FYI, I already started removing Python 2 support in
many of the packages I maintain (currently only uploaded to
On 4/15/19 9:24 AM, Hideki Yamane wrote:
> On Sun, 14 Apr 2019 21:11:09 +0200
> "Dr. Tobias Quathamer" wrote:
>> I think it's the right decision of the release team to stick with golang
>> 1.11 for buster. The previous migration from golang 1.10 to 1.11 took us
>> about four weeks until we had
On Sun, 14 Apr 2019 21:11:09 +0200
"Dr. Tobias Quathamer" wrote:
> I think it's the right decision of the release team to stick with golang
> 1.11 for buster. The previous migration from golang 1.10 to 1.11 took us
> about four weeks until we had fixed all packages with new FTBFS bugs.
Can we
Am 14.04.19 um 18:15 schrieb Mattia Rizzolo:
> You shouldn't really complain to the release team, but rather to the
> golang maintainers, that couldn't manage to move everything off golang
> 1.11 in time.
Just for the record, upstream has released golang 1.12 on February 25,
so only about two
On Sun, Apr 14, 2019 at 12:00:18PM +0100, Toni Mueller wrote:
> I strongly think that this decision very wrong and should be reversed.
> If the RT absolutely insist on cutting down the number of Go versions, I
> am not opposed to see eg. golang-1.11 go, however, as I don't see a
> compelling case
Hi,
On Sat, Apr 13, 2019 at 09:54:18PM +0800, Shengjing Zhu wrote:
> FWIW, golang-1.12 was removed from buster, because the RT think
> there're too many golang for buster[1].
there's no logic in that, and especially with the introduction of this
new feature, which the Go community has awaited
On Sat, Apr 13, 2019 at 09:54:18PM +0800, Shengjing Zhu wrote:
> FWIW, golang-1.12 was removed from buster, because the RT think
> there're too many golang for buster[1].
> At first we have golang-1.{10,11,12} in testing.
>
> [1]
On Sat, Apr 13, 2019 at 8:12 PM Toni Mueller wrote:
>
>
> Hello,
>
> I just figured that Buster is, from the current POV, going to ship with
> Golang 1.11. While I am new to Go, I figured that we should probably
> have a newer version of Golang in Buster, as they are now doing
> versioned
Hello,
I just figured that Buster is, from the current POV, going to ship with
Golang 1.11. While I am new to Go, I figured that we should probably
have a newer version of Golang in Buster, as they are now doing
versioned dependencies, but only starting with 1.12 or 1.13 (not quite
sure about
10 matches
Mail list logo
