The staleness gate compared only the toolkit major, so a host with
glibc >= 2.41, a CUDA 13.0/13.1/13.2 toolkit and a cu13-capable driver
kept that toolkit and skipped the CUDA 13.3 provisioning. The build then
hit the rsqrt header clash this script exists to avoid, and GGUF
inference stayed on the CPU server.
The gate now parses the toolkit minor and flags a 13.0-13.2 toolkit when
the detected glibc is 2.41 or newer (getconf first, ldd as a fallback;
an unparseable version keeps the previous major-only behavior). The
driver check still applies, so a host whose driver cannot run cu13 is
never pushed onto a 13.3 install.
Verified over the (toolkit release) x (glibc) x (driver major) matrix
with mocked nvcc output: 13.0/13.1/13.2 on glibc >= 2.41 are stale;
13.3, 13.4 and a two-digit 13.10 are kept; the same toolkits on older
glibc are kept; pre-13 stays stale on any glibc; and nothing is flagged
when the driver reports CUDA 12.x. Version parsing verified for 2.39,
2.41, 2.42, 3.0, empty and garbage inputs.
8d3735eddc