Author	SHA1	Message	Date
pat-s	8140702b5f	chore(alpine): drop the deprecated Alpine 3.22 slot ... Alpine 3.22 is deprecated and is no longer a published slot. It was never routed: `local.rpkgs_slots` in `cdn.tf` lists eight distros and alpine322 is not among them, so `UNION_SLOTS` never gated per-minor rewriting for it and every request fell through to the flat index. The fleet-wide routing verification made that concrete. Across all 16 published slots, both architectures, three R minors and both contractual URL forms, 1056 of 1056 install-and-load checks passed. Every failure in the run was alpine322, identical on amd64 and arm64, and identical across `arch`, `generic` and `flat`. That last part is the signature of an unrouted slot: on a routed slot the contractual forms diverge from `flat`, because the divergence is the routing. Its flat objects are R 4.5 builds, so R 4.4 and R 4.6 clients got `LOAD_FAILED` while R 4.5 clients were fine. This change will: - Remove the alpine-322 matrix rows and dropdown options from every pipeline that carried them, so `=all` no longer fans out to a slot nobody can reach. - Remove `3.22` from the `OS_VERSION` dropdowns in `build-all-versions.yaml` and `repair-built-stamp.yaml`, and move the latter's default to `3.23`. - Update the stale `3.22` examples in `local/packages-to-build.R`. The six alpine-322 cron jobs are deleted from the Crow server as well, since a cron whose matrix row is gone would keep firing against nothing: 5 process-cran-updates-alpine-322-amd64 0 5/8 * * * 6 process-cran-updates-alpine-322-arm64 30 5/8 * * * 68 weekly-audit-missing-alpine-322-amd64 20 0 * * 0 69 weekly-audit-missing-alpine-322-arm64 30 0 * * 0 82 weekly-rebuild-missing-alpine-322-amd64 0 4 * * 0 83 weekly-rebuild-missing-alpine-322-arm64 10 4 * * 0 The published objects and indexes under `amd64/alpine322` and `arm64/alpine322` are left in place; removing them from the bucket is a separate decision.	2026-09-11 07:25:21 +00:00
pat-s	ee4562d44c	feat(abi): repair from the recorded verdicts rather than an ad-hoc scan (#206) ... ## Why The reprex found 44 routed-path failures: `Rcpp`, `Matrix` and `RJSONIO` served to R 4.4 from 4.5 builds. Two causes, both now fixed (#205 here, #129 in bincraft) — but the repair itself also needs redoing, and the lists it ran from no longer exist. Those lists came from a one-off local symbol scan, seeded from a candidate set derived on a single slot. That made them a lower bound by construction: the scan found 846 package-slot pairs, while inspecting every object found **4077** unsafe. `abi_flat_safety` now holds the authoritative answer for every slot, written by the flat-safety backfill from the binaries themselves: ``` 95418 inspected, 91325 safe, 4077 unsafe (4.3%) ``` against the 93% of compiled packages the source classifier suspects. ## What it does - `local/list-unsafe-flat-objects.R` prints the objects recorded as unable to load under some minor, for one slot. - The workflow rebuilds each under **every** R minor installed in the image, with **no `--sensitive-only` gate**. Since bincraft v5.3.0 the destination is decided by the built binary's symbols, so a package needing a per-minor slot lands there and a portable one lands in the flat slot. Gating on the source classifier is exactly what let `Rcpp` slip through. ## Safety It **fails loudly when a slot has no verdicts at all**, rather than printing an empty list. An empty repair list is indistinguishable from "nothing to repair" and would read as success while doing nothing — the same shape of silent failure as the missing `PGPASS`. `crow lint` passes. ## After this Run it fleet-wide, re-index, then re-run the reprex. The routed paths are the ones that must come back clean; the `flat` form's failures are the separate prune question. Reviewed-on: #206	2026-09-07 18:46:50 +00:00