The 1.60.0 debs were built against glibc 2.39 and never installed on the
bookworm fleet; rather than force-moving the tag, the rebuilt release
ships as 1.60.1. Nothing was published to crates.io at 1.60.0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The floor gate's second grep matched the trailing digit of the package
name before the version ('libc6 (>= 2.34)' -> '6'), failing every
target. sed capture group instead; verified against realistic Depends
strings.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The v1.60.0 debs failed to install on Raspberry Pi OS bookworm:
socktop : Depends: libc6 (>= 2.39) but 2.36-9+rpt2+deb12u14 is to be installed
Cross-compiled binaries link against the RUNNER's (multiarch) glibc, so
the runner picks the minimum glibc the packages demand. ubuntu-latest
migrated from 22.04 (glibc 2.35) to 24.04 (glibc 2.39) between the
1.50.x releases and now, silently raising the requirement past the
Debian-12 fleet.
Pin the build job to ubuntu-22.04 (2.35 — satisfied by bookworm's 2.36)
and add a post-build gate that reads each .deb's computed libc6
requirement and fails the run if it exceeds the fleet floor, so the next
runner migration turns into a red build instead of a fleet-wide apt
error.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jasonwitty