Reviewed 2026-10-04. The module still requires Go 1.27.0. The installer checks only that git and go exist and prints go version, then builds with the inherited toolchain policy. The existing isolated-host comment confirms an older Go succeeds with default automatic toolchain download; this is not a general fresh-host build failure. Remaining scope: when automatic selection/download is disabled or unavailable, explain the required version and the actual toolchain failure clearly before installing partial binaries. Preserve automatic selection rather than imposing an unnecessary version prerequisite. Current review verified source, not an offline installation.
Acceptance criteria
An older default Go with automatic toolchain selection can still install. With local-only selection or an unavailable download, installation reports required Go 1.27.0 and the actual failure before installing partial binaries.
Imported from beads archie-core-7m2a · GitHub #1096 · type bug · priority P2 · created 2026-09-22 · closed 2026-10-17
Reviewed 2026-10-04. The module still requires Go 1.27.0. The installer checks only that git and go exist and prints go version, then builds with the inherited toolchain policy. The existing isolated-host comment confirms an older Go succeeds with default automatic toolchain download; this is not a general fresh-host build failure. Remaining scope: when automatic selection/download is disabled or unavailable, explain the required version and the actual toolchain failure clearly before installing partial binaries. Preserve automatic selection rather than imposing an unnecessary version prerequisite. Current review verified source, not an offline installation.
### Acceptance criteria
An older default Go with automatic toolchain selection can still install. With local-only selection or an unavailable download, installation reports required Go 1.27.0 and the actual failure before installing partial binaries.
### Close reason
b293bf5c
---
_Imported from beads `archie-core-7m2a` · GitHub #1096 · type bug · priority P2 · created 2026-09-22 · closed 2026-10-17_
sam
added the mediumbug labels 2026-10-27 13:39:07 +00:00
CORRECTION from the isolated-host run, and it changes the finding: this is NOT 'clean hosts fail'. On a disposable incus container (Debian 12, its own loopback) with Go 1.25.14 and the DEFAULT GOTOOLCHAIN=auto, the 'go 1.27.0' directive made Go download golang.org/toolchain@v0.0.1-go1.27.0.linux-amd64 and the build proceeded: install.sh completed exit 0, all six binaries were built, and a full archie-update-install completed afterwards. So install.sh needs no version check WHEN THE TOOLCHAIN CAN BE FETCHED, and the failure first observed was environmental - GOTOOLCHAIN=local, a blocked toolchain download, or an offline host. The remaining value here is DIAGNOSTICS, not a precondition: when the toolchain cannot be fetched, the operator gets a message about go.mod and running go 1.25.14 that reads like user error. Handle it so the failure says what is actually wrong (no toolchain available and why), and do not record the requirement as 'a clean host cannot build' - a clean host with default settings succeeds.
_sam wrote (originally 2026-09-22):_
CORRECTION from the isolated-host run, and it changes the finding: this is NOT 'clean hosts fail'. On a disposable incus container (Debian 12, its own loopback) with Go 1.25.14 and the DEFAULT GOTOOLCHAIN=auto, the 'go 1.27.0' directive made Go download golang.org/toolchain@v0.0.1-go1.27.0.linux-amd64 and the build proceeded: install.sh completed exit 0, all six binaries were built, and a full archie-update-install completed afterwards. So install.sh needs no version check WHEN THE TOOLCHAIN CAN BE FETCHED, and the failure first observed was environmental - GOTOOLCHAIN=local, a blocked toolchain download, or an offline host. The remaining value here is DIAGNOSTICS, not a precondition: when the toolchain cannot be fetched, the operator gets a message about go.mod and running go 1.25.14 that reads like user error. Handle it so the failure says what is actually wrong (no toolchain available and why), and do not record the requirement as 'a clean host cannot build' - a clean host with default settings succeeds.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reviewed 2026-10-04. The module still requires Go 1.27.0. The installer checks only that git and go exist and prints go version, then builds with the inherited toolchain policy. The existing isolated-host comment confirms an older Go succeeds with default automatic toolchain download; this is not a general fresh-host build failure. Remaining scope: when automatic selection/download is disabled or unavailable, explain the required version and the actual toolchain failure clearly before installing partial binaries. Preserve automatic selection rather than imposing an unnecessary version prerequisite. Current review verified source, not an offline installation.
Acceptance criteria
An older default Go with automatic toolchain selection can still install. With local-only selection or an unavailable download, installation reports required Go 1.27.0 and the actual failure before installing partial binaries.
Close reason
b293bf5cImported from beads
archie-core-7m2a· GitHub #1096 · type bug · priority P2 · created 2026-09-22 · closed 2026-10-17sam wrote (originally 2026-09-22):
CORRECTION from the isolated-host run, and it changes the finding: this is NOT 'clean hosts fail'. On a disposable incus container (Debian 12, its own loopback) with Go 1.25.14 and the DEFAULT GOTOOLCHAIN=auto, the 'go 1.27.0' directive made Go download golang.org/toolchain@v0.0.1-go1.27.0.linux-amd64 and the build proceeded: install.sh completed exit 0, all six binaries were built, and a full archie-update-install completed afterwards. So install.sh needs no version check WHEN THE TOOLCHAIN CAN BE FETCHED, and the failure first observed was environmental - GOTOOLCHAIN=local, a blocked toolchain download, or an offline host. The remaining value here is DIAGNOSTICS, not a precondition: when the toolchain cannot be fetched, the operator gets a message about go.mod and running go 1.25.14 that reads like user error. Handle it so the failure says what is actually wrong (no toolchain available and why), and do not record the requirement as 'a clean host cannot build' - a clean host with default settings succeeds.