Related Issues and Documentation

• go/build: add go1.2 build tag #6449 (closed)
• x/website: doc/install/source instructions don't work due to distribution (ubuntu 22.04) provided go (go1.18.1) being too old #65654 (closed)
• website: go1.22.0.linux-amd64.tar.gz contains wrong go version (go1.21.4) #65837 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

Duplicate of #68834

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For questions please refer to https://github.com/golang/go/wiki/Questions

This is not a question, this a bug report.

As far as we can tell, it's something specific to your environment that you're not telling us about, since the instructions you provided do not reproduce the issue.
Regardless, as it's an out of support version, it's not going to see any more commits, and the error for the current version is correct.

Perhaps someone in the forums would be willing to troubleshoot your issue.

Thanks. I tried on a clean environment and wasn't able to reproduce the issue. I then ran a build with strace which revealed the problem.
So the build system scans the filesystem and if it finds .git directory somewhere (even if it is outside of the go sources location) it assumes there is git involved somehow, it then runs git status --porcelain which returns fatal: not a git repository (or any of the parent directories): .git (with exist code 128) which build system treats as an error. This is where the bug is.
So the bug is definitely there (in how vcs is detected), but oh well, it is an ancient software and at least it can be worked around.

Thanks for your help.