-
Couldn't load subscription status.
- Fork 599
[3.0] Upgrade vitess and rebuild gh, moby-containerd-cc with golang-1.25.3 #14639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 3.0-dev
Are you sure you want to change the base?
Conversation
8c42034 to
2ae6350
Compare
587d26d to
b77a169
Compare
| BuildRequires: go-md2man | ||
| BuildRequires: make | ||
| BuildRequires: systemd-rpm-macros | ||
| BuildRequires: glibc-static >= 2.38-13%{?dist} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain more about this, and why this change was needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After enabling CGO, the build failed again with the following errors:
/usr/bin/ld: cannot find -lresolv: No such file or directory
/usr/bin/ld: cannot find -lc: No such file or directory
This indicates that the static libraries for libc and libresolv are missing.
To resolve this, added the glibc-static package, which provides -lc and -lresolv.
|
|
||
| %build | ||
| export BUILDTAGS="-mod=vendor" | ||
| export SHIM_CGO_ENABLED=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please explain + comment what this is for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When rebuilding moby-container-cc with golang-1.25.1, the build failed due to this error:
(untyped string constant "\n\tUsing a crypto backend requires CGO_ENABLED=1.\n\t..." is not used).
To fix this, enabled CGO by setting "export SHIM_CGO_ENABLED=1".
| Name: vitess | ||
| Version: 19.0.4 | ||
| Release: 7%{?dist} | ||
| Version: 21.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the rationale on selecting this version? Does 19.0.4 not compile with a newer golang? (Do we know why?)
Also note that 21.0.x is now on 21.0.3--and it will be EOL in ~1 month.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when vitess-19.0.4 build tried with newer golang, build has failed due to following error:
"link: vitess.io/vitess/go/hack: invalid reference to runtime.roundupsize"
The issue is mentioned in vitessio/vitess#16015.
Vitess makes use of the Go runtime's internal roundupsize symbol via go:linkname. Go 1.22+ significantly restricts this kind of linking; the symbol is not exported for external linking, causing the build/link to fail.
this linkname is removed in vitessio/vitess#16016
3abc713 to
683428c
Compare
SPECS/gh/gh.spec
Outdated
| %{_datadir}/zsh/site-functions/_gh | ||
|
|
||
| %changelog | ||
| * Tue Sept 09 2025 Jyoti Kanase <[email protected]> - 2.62.0-10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you please change Sept to Sep
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed.
SPECS/golang/golang.spec
Outdated
| Summary: Go | ||
| Name: golang | ||
| Version: 1.25.1 | ||
| Version: 1.25.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should skip 1.25.2 due to the following issue: golang/go#75828 (comment)
There is another PR up for 1.25.3 already - #14863
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once #14863 is merged, I will remove the golang-1.23.2 changes from this PR.
ef70524 to
f5e6b0b
Compare
f5e6b0b to
bcbdff9
Compare
bcbdff9 to
9542899
Compare
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
Upgrade vitess and rebuild gh, moby-containerd-cc with golang-1.25.1
Change Log
Does this affect the toolchain?
YES/NO
Associated issues
Links to CVEs
Test Methodology