VACUUM snapshot metadata through the sqlite driver, not a CLI (closes #120)

snapshot create compacted the metadata database by running a sqlite3 command-line binary, after every blob had already been uploaded. On a host without that binary, which includes anyone who installed with go install, the backup failed at the last step, and two tests failed the same way. VACUUM now runs through the Go sqlite driver the program already uses, and its error is returned to the caller. The runtime Docker image no longer installs the sqlite package, since nothing in the binary calls it. model: claude-opus-4-8 (implementation, review); claude-fable-5-1 (merge)
2026-09-21 19:41:28 +02:00
parent bdce350041
commit 3d56dd7eb0
7 changed files with 131 additions and 16 deletions
@@ -114,9 +114,6 @@ main() {
    # from CI. Nothing on the host is ever used as a linter, at any
    # version, so installing one here would buy nothing.

-    # sqlite3 CLI: the test suite shells out to it (VACUUM).
-    if missing sqlite3; then pkg_install sqlite sqlite3 sqlite sqlite; fi
-
    # goreleaser, at the version pinned by script/install-goreleaser and
    # verified against a hardcoded sha256. Package managers are not used
    # for it: they ship whatever version they happen to carry, and the