feat: per-suite archive host and keyring in SUITES #2
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/multi-archive-keyrings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
acng on c2-talos also caches Ubuntu (noble/questing) for CI, but butler could only verify against deb.debian.org + debian-archive-keyring, leaving those suites unwatched.
SUITES entries are now
<archive>|<suite>[|<keyring>]:/or.is used verbatim as host/path, e.g.archive.ubuntu.com/ubuntuorsecurity.ubuntu.com/ubuntudebian(default),ubuntu, or an absolute keyring pathubuntu-keyringis installed alongsidedebian-archive-keyring(it ships in the Debian archive, so the install stays direct-from-upstream and isolated from the proxy under test); it is only exercised when SUITES lists Ubuntu suites.Verified:
hack/validate.shpasses (configmap regenerated, both render paths ok); parse logic unit-tested against all entry forms; Debian trixie ubuntu-keyring 2023.11.28.1 validates the current noble/questing InRelease signatures.Motivation: c2-talos incident 2026-07-22/23 — acng range-resume splicing corrupted trixie-updates/trixie-security InRelease twice in 12h; Ubuntu suites currently have no equivalent watchdog. Companion infra PR extends the c2-talos SUITES patch once this merges.
🤖 Generated with Claude Code