Fix publish-deb glibc mismatch (run on ubuntu-24.04)#14
Merged
Conversation
The publish-deb workflow has been failing on every release since the
job was added: `taiki-e/install-action` pulls a prebuilt cargo-deb
binary that's linked against glibc 2.39, but ubuntu-22.04 ships glibc
2.35. The job dies in the "Install cargo-deb" step with:
cargo-deb: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39'
not found (required by cargo-deb)
ubuntu-24.04 ships glibc 2.39, matching what cargo-deb expects.
Bumping the runner is the smallest fix; we don't have to coordinate
with cargo-dist's separate build matrix (which is fine on
ubuntu-22.04 because cargo-dist's own cross-compile uses an older
glibc by design via the manylinux2014 zig setup).
Affects only the publish-deb workflow. After this merges, the next
release will attach qn_X.Y.Z_amd64.deb and qn_X.Y.Z_arm64.deb to the
GitHub Release.
alehlopeh
approved these changes
Jun 11, 2026
yorsant
approved these changes
Jun 11, 2026
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
3 participants
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.
Summary
custom-publish-debhas been failing on every release since the job was added (v0.1.3, v0.1.2, v0.1.1 — see release run 27030643090). The job dies after ~6 seconds with:taiki-e/install-actionpulls a prebuilt cargo-deb that's linked against glibc 2.39, butubuntu-22.04ships glibc 2.35.ubuntu-24.04ships 2.39, matching.This is isolated to the publish-deb workflow — cargo-dist's own cross-compile matrix is fine on 22.04 because it uses zig + manylinux2014 to target an older glibc by design.
Test plan
runs-on: ubuntu-22.04→ubuntu-24.04(plus a comment explaining why).qn_X.Y.Z_amd64.debandqn_X.Y.Z_arm64.debto the GitHub Release page.dpkg --info qn_X.Y.Z_amd64.debon the downloaded asset shows clean metadata (Package: qn, correct version,/usr/bin/qn).