[home] Note that pi 0.80.5 still has the Bun --compile issue

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

diff --git a/TODO b/TODO
index 2f7226af8ae32456f442494470b0202051696ac0..32c1fed72ce56fc7a5bc8e525192868f41c1a596 100644 (file)
--- a/TODO
+++ b/TODO
@@ -17,10 +17,12 @@ TODO
 
 * Go back to the upstream pi release tarball once Bun's --compile bug is
   fixed.  Bun 1.2.20-1.3.11 produces broken binaries; 1.3.14 fails
 
 * Go back to the upstream pi release tarball once Bun's --compile bug is
   fixed.  Bun 1.2.20-1.3.11 produces broken binaries; 1.3.14 fails

-  entirely on this system (kernel 7.0.12, glibc 2.39).  When a fixed Bun
-  is available, just download the tarball, extract the binary, and wrap it
-  -- no build step needed.  Remove the npm-install-build-system wrapper
-  and the Node.js dependency in conf/home/pi.scm.
+  entirely on this system (kernel 7.0.12, glibc 2.39).  As of pi 0.80.5
+  (2026-07-09), the upstream CI still builds with Bun 1.3.10, so the
+  problem persists.  When a fixed Bun is available, just download the
+  tarball, extract the binary, and wrap it -- no build step needed.
+  Remove the npm-install-build-system wrapper and the Node.js dependency
+  in conf/home/pi.scm.

 
 * Move configuration files to the Guix store and bundle them with the
   binary.  This requires redesigning home-program-configuration so
 
 * Move configuration files to the Guix store and bundle them with the
   binary.  This requires redesigning home-program-configuration so