kevinveenbirkenbachandClaude Opus 5.5 34506554f7 fix(cache): download pacman packages per node and publish them into the shared cache ...

The shared pacman cache was the first writable CacheDir on every arch runner and lab node. Our arch image sets DisableSandbox, so libalpm downloads straight into that directory (util.c _alpm_download_dir_setup only makes a per-process temp dir with the sandbox on), and the XferCommand writes <pkg>.part there with curl -C -o %o; two nodes fetching the same package appended to the same .part file, and the second rename failed or left a corrupt package in the shared cache.

pacman.sh now gives each node its own download directory <shared>/pacman/node-XXXXXX/ (created once with mktemp, reused from pacman.conf on later runs) as the CacheDir between the read-only host layer and <shared>/pacman/, and writes a PostTransaction hook to pacman.d/hooks/infinito-shared-cache.hook that renames every finished package and signature into <shared>/pacman/; .part files stay for the next resume. Both directories sit in one bind mount, so each publish is an atomic rename(2). pacman.sh fails when pacman.conf sets HookDir, since pacman would then skip the hook silently. Requirement 065 and cache.md describe the three layers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-30 22:43:01 +01:00

..

package-frontend

test(cache): point the CA test at the path the script was moved to

2026-10-16 00:22:13 +02:00

__init__.py

fix(cache): install CA anchors where every update-ca-trust family reads them

2026-10-15 23:45:53 +02:00

test_pacman.py

fix(cache): download pacman packages per node and publish them into the shared cache

2026-10-30 22:43:01 +01:00

test_registry_ca.py

fix(cache): install CA anchors where every update-ca-trust family reads them

2026-10-15 23:45:53 +02:00