Actions don't run in a shell, so in order to expand the environment
variable it is necessary to wrap the command in a shell invocation.
Signed-off-by: Nikola Forró <nforro@redhat.com>
In the previous PackIt attempt, the sources were not properly updated.
Fix Version field
Remove 0001-Disable-Google-s-proxy-sumdb-and-toolchain.patch
Remove baserelease macro
Update bundled-deps.sh to follow the versioning guidelines
Upstream tag: go1.21.0
Upstream commit: c19c4c56
If you need to do any change in this pull request, you need to locally fetch the source branch of it and push it (with a fix) to your fork (as it is not possible to push to the branch created in the Packit’s fork):
```
git fetch https://src.fedoraproject.org/forks/packit/rpms/golang.git refs/heads/*:refs/remotes/packit/*
git checkout packit/1.21.0-rawhide-update-pull_from_upstream
```
```
Error:
Problem: package golang-race-1.19.7-1.fc37.x86_64 requires golang = 1.19.7-1.fc37, but none of the providers can be installed
- golang-1.19.7-1.fc37.x86_64 does not belong to a distupgrade repository
- problem with installed package golang-race-1.19.7-1.fc37.x86_64
```
The Go runtime silently chose the gold linker on arm and aarch64 build
targets to work around a binutils bug.
That bug was from 2016, and has been fixed in binutils for a while. But
the Go workaround was still in place.
The workaround to choose gold was supposed to error out during the
configure phase if gold wasn't found - but that doesn't happen.
This leads to builds on aarch64 failing if attempting to compile without
gold.
Just removing the special condition in the Go source code:
https://go-review.googlesource.com/c/go/+/391115/
works, but that patch is unlikely to be merged upstream.
A patch fixing the build is more likely to be merged:
https://go-review.googlesource.com/c/go/+/366279/
which updates the linker selection to use gold only if available.
References to this bug in upstream Go and Binutils:
https://github.com/golang/go/issues/22040https://sourceware.org/bugzilla/show_bug.cgi?id=19962
Including the likely-to-be-merged patch here.