Update glibc to 2.44 - #529
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Update glibc 2.43 → 2.44
Note
glibcdeclaresreplace_on_cycle, so it participates in the toolchainrebuild graph and one hash change cascades through the set. 325 of 433 packages
reference glibc — expect a fleet-wide rebuild.
Summary
2.432.44gnu:glibcPer-package details
glibc 2.43 → 2.44d9c86c6b5dbddb43a3e08270c5844fc5177d19442cf5b8df4be7c07cd5fa3831→37f600f2bef3c5e8300147059568b2a2e40a7ad6ccc65ce942556d49429cc667gs://minimal-staging-archives/glibc-2.43.tar.xz→gs://minimal-staging-archives/glibc-2.44.tar.xz(GPL-2.0-only AND LGPL-2.1-only)pkgmgr mirror --package glibc --version 2.44(pkgmgr-rs#588); sha256 verified against ftp.gnu.orgPre-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-qualifiersbreak (pkgs#238) and the same class was the main risk here.Built in a clean-room
minsession (minimal0.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:Every non-pass was infrastructure, and each was confirmed:
codex,node,node-lts,ruff,uv,zig) — sandbox OOM on a 15.6 GiB VM. Re-run at 22 GiB:ast-grep,atuin,bandwhichall pass.bun, andhunk/opencodewhich 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 atarthat tries tochownto uid 1000, which the sandbox refuses.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:, nodiscarded-qualifiers, no undefined references anywhere in 312 builds — the 2.43-class breakage does not recur.🤖 Generated with Claude Code