test0r
7bb2fbeca9
build and publish packages / distcc-avahi-aarch64 (push) Successful in 35s
build and publish packages / lmcp-any (push) Successful in 7s
build and publish packages / lmcp-debian (push) Successful in 5s
build and publish packages / claude-his-any (push) Successful in 7s
build and publish packages / ffmpeg-v4l2-request-aarch64 (push) Successful in 12m18s
build and publish packages / claude-his-debian (push) Successful in 5s
Earlier framing was wrong — the wall isn't 'Arch ARM clang 22 vs Arch x86_64 clang 23'. Arch x86_64 is also on 22.1.3; LLVM 23 isn't anywhere in extra/staging. The flags chromium 147 emits come from chromium's clang fork (Google maintains an LLVM fork with chromium-specific passes), not upstream LLVM 23. PKGBUILD'ing clang 23 is the wrong tree. Right tree: cross-compile from x86_64 so chromium's bundled clang prebuilt is reachable. CIPD has full linux-amd64 prebuilts, gclient sync works cleanly, no qemu-x86_64-static dance needed. his provisioned CT 220 chromium-builder-x86 on data (Ryzen 7 1700, 14 cores, 32 GiB RAM, 200 GiB ZFS). data is normally asleep — woke via /opt/herding/bin/wake-data. Reach pattern: hertz -> ssh data -> pct exec 220. Source fetch running as chromium-fetch.service transient unit on CT 220. Once src is in, plan: tools/clang/scripts/update.py for chromium's bundled clang + arm64 sysroot, gn gen with target_cpu=arm64, build, transfer aarch64 binary to ohm/fresnel/ampere. boltzmann chromium-builder LXD container preserved as fallback; can be torn down if cross-compile pans out. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
marfrit-packages
Overlay package repository for the reauktion.de infrastructure.
Published at: https://packages.reauktion.de/
Scope
| Tree | Arches | Notes |
|---|---|---|
| Arch Linux ARM (ALARM) | aarch64 |
primary target — Pi 5, Rock 5, ampere, KU-1255 test rigs |
| Arch Linux | x86_64 |
for nuccies / workstations |
| Debian | arm64, amd64 |
for non-Arch hosts |
MIPS is intentionally unsupported. The Fritz!Box is sacred.
Layout (served at packages.reauktion.de)
packages.reauktion.de/
├── arch/
│ ├── aarch64/{marfrit.db,marfrit.files,*.pkg.tar.{xz,zst}{,.sig}}
│ └── x86_64/...
├── debian/
│ ├── dists/
│ │ ├── bookworm/{Release,InRelease,Release.gpg,main/binary-{arm64,amd64}/...}
│ │ └── trixie/...
│ └── pool/main/...
└── marfrit.gpg # public signing key
Adding the repo (Arch / ALARM)
curl -sO https://packages.reauktion.de/marfrit.gpg
sudo pacman-key --add marfrit.gpg
sudo pacman-key --lsign-key 92D5E96D8F63C75E4116AA1FF5C8C4603D0D250C
# Paste at the end of /etc/pacman.conf:
[marfrit]
Server = https://packages.reauktion.de/arch/$arch
SigLevel = Required DatabaseRequired
sudo pacman -Sy
Adding the repo (Debian)
sudo install -m 755 -d /etc/apt/keyrings
curl -s https://packages.reauktion.de/marfrit.gpg | \
sudo gpg --dearmor -o /etc/apt/keyrings/marfrit.gpg
echo "deb [signed-by=/etc/apt/keyrings/marfrit.gpg] https://packages.reauktion.de/debian $(lsb_release -cs) main" | \
sudo tee /etc/apt/sources.list.d/marfrit.list
sudo apt update
Signing key
- Fingerprint:
92D5E96D8F63C75E4116AA1FF5C8C4603D0D250C - UID:
Markus Fritsche (marfrit-repo signing) <mfritsche@reauktion.de> - Expires: 2030-04-13
Key management procedures (renewal, rotation, revocation) live in DokuWiki at private:reauktion:marfrit_repo_key (admin-only).
Layout in this Git repo
marfrit-packages/
├── README.md
├── arch/
│ └── distcc-avahi/ # ALARM distcc with --with-avahi
├── debian/ # (future) Debian source packages
└── .gitea/
└── workflows/
└── build.yml # CI pipeline stub
mfritsche@reauktion.de.