Repository navigation
fix: restore Linux glibc 2.17 release builds for v0.3.1 - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both Linux builds in the v0.3.0 release run fail with
undefined symbol: renameat2. The archive restore path references the glibc 2.28 wrapper while release artifacts target glibc 2.17.Invoke the same Linux
renameat2operation throughsyscall, preserving atomicRENAME_NOREPLACEand refusal on unsupported kernels. Bump the workspace and local lockfile versions to v0.3.1 so the existing v0.3.0 tag remains unchanged.Validation: reproduced the exact glibc 2.17 link failure; both Linux release targets now build with pinned Zig 0.13.0/cargo-zigbuild 0.24.0 and require at most GLIBC_2.17. All 13 archive CLI tests, formatting and workspace clippy pass. The ARM64 release binary passes capture/verify/restore byte-and-mode checks and refuses an existing destination. Platform CI runs on this PR; release publication remains a separate step.