Repository navigation
fix(release): use the build host's glibc as the linux ceiling - #187
Merged
Merged
Conversation
Upstream v0.1.10 caps packaged Linux binaries at glibc 2.39 for its Ubuntu 24.04 release jobs. 456code stages its AppImage on the machine that runs it, so furnace's newer glibc failed every staged build. The ceiling is now the build host's own glibc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Since the v0.1.10 merge the furnace stager fails every AppImage build, because upstream's new packaging check caps Linux binaries at glibc 2.39 (its Ubuntu 24.04 release jobs) and furnace builds node-pty against glibc 2.44. 456code only stages the AppImage on the machine that runs it, so the ceiling is now the build host's own glibc, read from the Node process report, and the existing scan test asks for 2.99 instead of 2.40. A binary needing glibc 2.42 failed the old check with the same error the stager logged and passes the new one. Claude Opus 5.5 via 456code.