Skip to content

Update glibc to 2.44 - #529

Merged
bryan-minimal merged 1 commit into
mainfrom
update/glibc-2.44
Jul 27, 2026
Merged

Update glibc to 2.44#529
bryan-minimal merged 1 commit into
mainfrom
update/glibc-2.44

Conversation

@bryan-minimal

Copy link
Copy Markdown
Member

Update glibc 2.43 → 2.44

Note

glibc declares replace_on_cycle, so it participates in the toolchain
rebuild graph and one hash change cascades through the set. 325 of 433 packages
reference glibc — expect a fleet-wide rebuild.

Pkgscan: clean — diff against the prior version surfaced no newly-introduced suspicious patterns.

Summary

Package Old New Source
glibc 2.43 2.44 gnu:glibc

Per-package details

glibc 2.43 → 2.44
  • SHA256: d9c86c6b5dbddb43a3e08270c5844fc5177d19442cf5b8df4be7c07cd5fa383137f600f2bef3c5e8300147059568b2a2e40a7ad6ccc65ce942556d49429cc667
  • Size: 19.7 MB (20,620,544 bytes)
  • Source: gs://minimal-staging-archives/glibc-2.43.tar.xzgs://minimal-staging-archives/glibc-2.44.tar.xz
  • Released: 2026-07-25 00:05:26 UTC
  • License: (GPL-2.0-only AND LGPL-2.1-only)
  • Mirrored: staged via pkgmgr mirror --package glibc --version 2.44 (pkgmgr-rs#588); sha256 verified against ftp.gnu.org

Pre-merge verification

Unusually for a libc bump, this one was rebuilt against the fleet before opening, because 2.43 caused an ecosystem-wide -Werror=discarded-qualifiers break (pkgs#238) and the same class was the main risk here.

Built in a clean-room min session (minimal 0.5.0-rc3.dev.6) on gcc 15, deliberately not bundled with the available gcc 16 bump so any failure would have exactly one candidate cause:

result count
Proven-clean rebuilds 312
Source-level failures 0

Every non-pass was infrastructure, and each was confirmed:

  • 6 × SIGKILL (codex, node, node-lts, ruff, uv, zig) — sandbox OOM on a 15.6 GiB VM. Re-run at 22 GiB: ast-grep, atuin, bandwhich all pass.
  • 3 × pre-existing (bun, and hunk/opencode which build through bun) — control-tested against stock glibc 2.43 and they fail there too, so unrelated to this bump. Root cause is bun's vendored build extracting Node with a tar that tries to chown to uid 1000, which the sandbox refuses.
  • 1 × timeout — harness wall-clock, not the package.

glibc itself was verified by artifact rather than exit code: the built library self-reports GNU C Library (GNU libc) stable release version 2.44.

No error:, no discarded-qualifiers, no undefined references anywhere in 312 builds — the 2.43-class breakage does not recur.

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fe4abdc1-f492-46b5-afb5-2ede8f2dcbe2

📥 Commits

Reviewing files that changed from the base of the PR and between 3136792 and 6750460.

📒 Files selected for processing (1)
  • packages/glibc/build.ncl
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch update/glibc-2.44

Comment @coderabbitai help to get the list of available commands.

@bryan-minimal
bryan-minimal added this pull request to the merge queue Jul 27, 2026
Merged via the queue into main with commit 545842f Jul 27, 2026
10 checks passed
@bryan-minimal
bryan-minimal deleted the update/glibc-2.44 branch July 27, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants