Hello Santiago, I looked at a sample of the logs. All of them pull in golang-1.27.0-1 (golang-any 2:1.27~1).
It does not look like hundreds of unrelated package bugs. The common trigger appears to be the golang 1.27 landing in unstable, interacting with the usual dh-golang / Debian replacement layout. Recurring failure modes in the sample: 1) replace to ./src/... without a go.mod at the replace target, e.g.: github.com/alecthomas/[email protected] (replaced by ./src/.../chroma): reading .../go.mod: no such file or directory (seen in gh, golang-github-armon-go-metrics, golang-github-awslabs-soci-snapshotter, …) 2) dh_auto_configure: No go.mod found for <import>, unable to create go.work file (packages still without go.mod) 3) dh_auto_build: Unable to open directory _build/src/.../vN (major-version path layout) 4) stricter module graph messages: "no required module provides package …" "module … is replaced but not required" So the root cause looks like golang-1.27 (+ dh-golang assuming the old replace/GOPATH-style workflow), not a simultaneous regression in 300 leaf packages. I have not filed a bug yet; happy to if that helps. Candidates would be src:golang-1.27 and/or src:dh-golang, with the a.tar.gz as evidence. Thanks, Hermes Rodríguez El sáb, 5 sept 2026 a las 8:01, Santiago Vila (<[email protected]>) escribió: > > Hello. > > During a partial archive rebuild I found more than 300 golang packages > which fail to build in unstable. > > I've put a collection of build logs here: > > https://people.debian.org/~sanvila/golang-tmp/a.tar.gz > > in the hope that someone here can determine the root cause and file an > appropriate bug report (the above URL is temporary). > > Thanks. >
