Re: Did golang really get upgraded to 1.16.2?

2021-04-10 Thread Alejandro Saez Morollon
Go 1.16 enables by default modules. In fact, in 1.17, GOPATH is going to be removed. https://github.com/golang/go/issues/41330 If you are building RPM packages, go-srpm-macros not only contains useful macros but it enables GOPATH. ___ devel mailing

Re: Did golang really get upgraded to 1.16.2?

2021-04-10 Thread Alejandro Saez Morollon
Totally my fault. Rawhide branch contained stuff related to 1.16 release candidates and I didn't properly check it. The same thing happens in F34. It should be already solved in rawhide and soon on F34. ___ devel mailing list --

Re: Did golang really get upgraded to 1.16.2?

2021-04-09 Thread Alejandro Saez Morollon
On 09/04/2021 15:36, Richard W.M. Jones wrote: On Fri, Apr 09, 2021 at 08:49:39PM +0800, yanqiy...@gmail.com wrote: Hi folks, I see some reports in FZUG community that this commit [1], supposed to update golang to 1.16.2 in its changelog, didn't change its tarball or n-v-r to new version. And

Re: Did golang really get upgraded to 1.16.2?

2021-04-09 Thread Richard W.M. Jones
On Fri, Apr 09, 2021 at 08:49:39PM +0800, yanqiy...@gmail.com wrote: > Hi folks,  > > I see some reports in FZUG community that this commit [1], supposed to > update golang to 1.16.2 in its changelog, didn't change its tarball or > n-v-r to new version. And actually builds to 1.16-2. > > Is it

Did golang really get upgraded to 1.16.2?

2021-04-09 Thread yanqiyu01
Hi folks,  I see some reports in FZUG community that this commit [1], supposed to update golang to 1.16.2 in its changelog, didn't change its tarball or n-v-r to new version. And actually builds to 1.16-2. Is it intended to fo the upgrade or the commit is just a normal rebuild with wrong