This is a tracking bug for Change: Golang 1.17 For more details, see: https://fedoraproject.org/wiki/Changes/golang1.17 Rebase of Golang package to upcoming version 1.17 in Fedora 35, including the rebuild of all dependent packages(the pre-release version of Go will be used for the rebuild if released version will not be available at the time of the mass rebuild). If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Today is the "Code complete (testable)" deadline in the Fedora Linux 35 release schedule: https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html If this Change is complete enough to be tested, please indicate this by setting this bug to the MODIFIED status. (If it is 100% complete, you can set it to ON_QA). If you wish to defer this Change to Fedora Linux 36, please needinfo bcotton.
@bcotton I was planning on doing a build on rawhide and then try it on f35 before the freeze. Does it sound ok? Is there any other alternative?
That works for me unless FESCo objects. I'll include that note in the list I give them tomorrow.
As I commented in the FESCo issue #2660 [0], 225 packages of ~1800 failed to build with Go 1.17.0 on rawhide. Not sure about the next steps. any tips? @bencotton [0] https://pagure.io/fesco/issue/2660#comment-748390
You already asked FESCo, so I'll defer to their guidance. In general, I would say that so long as none of the FTBFS packages are in the critical path, it's fine to move forward with that level of failures and work with package owners to fix them. But since we're days away from Beta freeze, it might be better to defer this.
Deferred to F36 by FESCo.
I submitted a new proposal because we are planning on having Go 1.18 instead of the original proposal with 1.17 https://fedoraproject.org/wiki/Changes/golang1.18
This change is replaced by #2037868.