Snap Store USN-8737-2: rebuild is enough (libc6 unpinned) - #32
Merged
Merged
Conversation
The Snap Store scan flagged staged libc6 against USN-8737-2 (noble 2.39-0ubuntu8.9). snapcraft.yaml does not pin libc6 or freeze apt sources, so no recipe change is required — rebuilding pulls the patched archive package. Comment and tests lock that contract in. Co-authored-by: Dominic Letz <dominicletz@users.noreply.github.com>
dominicletz
marked this pull request as ready for review
September 11, 2026 13:42
Keep the libc6 USN rebuild contract covered on every PR. Co-authored-by: Dominic Letz <dominicletz@users.noreply.github.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
2 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
A Snap Store scan flagged
libc6in publisheddiode-noderevisions against USN-8737-2 (GNU C Library on Ubuntu 24.04 LTS,libc62.39-0ubuntu8.9).A simple rebuild will fix this. No recipe change is required for the update to land.
Reviewed
snap/snapcraft.yaml:base: core24matches noble (the USN-8737-2 release).libc6is listed inbuild-packagesandstage-packageswithout a version pin.package-repositoriesblock that would freeze the Ubuntu archive.Snapcraft therefore pulls the current archive
libc6at build time. Rebuilding all architectures and releasing the new revisions (edge, then candidate/stable) resolves the scan.libc6stays instage-packageson purpose: Snapcraft only stages packages that are explicitly listed; otherwise the snap would usecore24's copy, which can lag the archive libc used when compiling Erlang/NIFs.Vendored code called out in the Canonical mail (
vendor/xmedialib, in-tree xturn,scripts/install_openssl.shOpenSSL 1.1.1w) is unrelated to this glibc USN. No updates there for 8737-2.Changes
libc6so it is not version-pinned later.test/snap/snapcraft_test.exsassertscore24, nopackage-repositories, and unpinnedlibc6in both package lists.DIODE_MINIMAL_TEST=1 mix test --no-start.After merge
Rebuild the snap (Launchpad / snapcraft.io) for amd64, arm64, ppc64el, s390x, and riscv64, then release the new revisions to edge and stable/candidate/beta.
Tests
DIODE_MINIMAL_TEST=1 mix test --no-start test/snap/snapcraft_test.exsStandalone ExUnit run of that file: 3 passed.