Răsfoiți Sursa

docs(flare): fleet is decoupled from the upstream apt PPA

The PPA shipped exactly one payload, /usr/bin/flare, which we overwrite with the
source build; any apt upgrade would have replaced the CLI under a running agent and
delivered the mixed-build handshake failure. All eight nodes now have the package
purged (so dpkg no longer owns the path), the flare source and lil-flare keyring
removed, and the running build at both paths; apt-get update is clean fleet-wide.
v0.2.1 is staged on all eight nodes with the licence files that used to come from
the package.
Alexander Korolev 2 zile în urmă
părinte
comite
e5ff45fa64
1 a modificat fișierele cu 34 adăugiri și 1 ștergeri
  1. 34 1
      specs/tech-architecture/flare-2026-11-16-upgrade.md

+ 34 - 1
specs/tech-architecture/flare-2026-11-16-upgrade.md

@@ -105,7 +105,40 @@ line is flag-for-flag identical to the pre-window one. `ds41-tp4` was launched
 persistent from the start.
 
 
-## 5. Not fixed by this upgrade
+## 5. Apt decoupling (2026-11-16)
+
+The upstream PPA (`https://ppa.local-inference-lab.ai noble/main`, keyring
+`/etc/apt/keyrings/lil-flare-archive.asc`, package `flare-inference`) shipped
+exactly one payload: **`/usr/bin/flare`**. We overwrite that file with our source
+build, so any `apt upgrade` would have replaced the CLI while the agent kept the
+old inode — the mixed-build handshake failure, delivered by apt. There is also no
+way for `apt-get install -y --only-upgrade flare-inference` to be "harmless": the
+package owns the path.
+
+All eight nodes were decoupled the same way:
+
+```bash
+cp -a /usr/bin/flare /tmp/flare-keep                  # our build
+sudo apt-get purge -y flare-inference                # removes the file it owns
+sudo install -m 0755 /tmp/flare-keep /usr/bin/flare   # ours, now unowned
+sudo rm -f /etc/apt/sources.list.d/flare.sources \
+           /etc/apt/keyrings/lil-flare-archive.asc
+```
+
+Result on every node: `dpkg -S /usr/bin/flare` → *no path found*, no `flare`
+apt source, no LIL key, `apt-get update` clean, `/usr/bin/flare` and
+`~/.local/lib/flare-agent/flare` both `3cd3f442…`. Unattended upgrades are
+disabled anyway (`APT::Periodic::Unattended-Upgrade "0"`), so the fleet now has
+no path by which an upstream build arrives uninvited: upgrades are manual,
+`/usr/local/share/hyperflare/v0.2.1` (staged on all eight nodes, with the bundled
+LICENSE/NOTICE/THIRD_PARTY_NOTICES replacing the purged package docs), and rollback
+is the single `.orig-20261116` generation.
+
+**Rebuilds are now entirely ours.** Bumping upstream means: watch the repo,
+rebuild, stage a new `vX.Y.Z`, swap with `host-scripts/flare-swap.sh`, restart the
+agents together, relaunch both persistent groups.
+
+## 6. Not fixed by this upgrade
 
 - `dgx4` still has the KingSpec XG7000-2TB 2242 whose stop-and-go prefill poisoned
   RoCE on the October package — unchanged by a runtime upgrade; see