#9904 Go 1.16 change tracking issue
Closed: Fixed by kevin. Opened by jcajka.

  • Describe the issue
    Ask that Go can be part of the mass-rebuild, i.e. rebase will land prior to it. I will run scratch rebuilds prior to that, making sure that the FTBFS are minimal.
    Change proposal: https://fedoraproject.org/wiki/Changes/golang1.16
  • When do you need this? (YYYY/MM/DD)
    2020-12-29
  • When is this no longer needed or useful? (YYYY/MM/DD)
    2021-01-20
  • If we cannot complete your request, what is the impact?
    There will be need to run side tag rebuild, that I would prefer to avoid due to the number of Go based packages.
    CC'ing @alexsaezm

@jcajka Thanks for filing the ticket and we will include this change as part of F34 mass rebuild.

Metadata Update from @mohanboddu:
- Issue tagged with: change-ack, changes, f34, mass rebuild, medium-gain, medium-trouble, ops

go1.16beta1 is now available in the rawhide. It seems to cause 43 new ftbfs, based on local rebuilds. I'm looking through them atm. I hope that the upstream will make available rc1 soon, prior to the mass-rebuild.

@jcajka Mass rebuild is scheduled for this Wed, jan 20th, please let us know your findings and suggestions before then.

Pinging @bookwar

@mohanboddu so far all seems good. From 43 packages that failed most looks like mostly packaging issues, related to gomodules being on by default now(13, generally speaking mostly due to not following Go packaging guidelines), there have been some broken deps(3) and some variations in the tests output format(leading to false positives). I haven't seen anything that would suggest any issue on the compiler or distro side(glibc, gcc,...).

Continuing going through the remaining ones.

@jcajka Thanks for the update, we will include it for whatever the latest of Go version in rawhide for mass rebuild which will start later today.

The mass rebuild is all done now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata