import/path: issue title

[berryk-sunlife]

Go version

https://go.dev/dl/go1.23.2.linux-amd64.tar.gz

Output of go env in your module/workspace:

11:56:47 go env
11:56:47 GO111MODULE=''
11:56:47 GOARCH='amd64'
11:56:47 GOBIN=''
11:56:47 GOCACHE='/opt/cloudbees/jenkins/.cache/go-build'
11:56:47 GOENV='/opt/cloudbees/jenkins/.config/go/env'
11:56:47 GOEXE=''
11:56:47 GOEXPERIMENT=''
11:56:47 GOFLAGS=''
11:56:47 GOHOSTARCH='amd64'
11:56:47 GOHOSTOS='linux'
11:56:47 GOINSECURE=''
11:56:47 GOMODCACHE='/var/cloudbees/application-data/jenkins/workspace/Development/Security-Examples/Hello-World/Go/Build-Hello-World-Go-Watch-Revive@tmp/go/pkg/mod'
11:56:47 GONOPROXY=''
11:56:47 GONOSUMDB=''
11:56:47 GOOS='linux'
11:56:47 GOPATH='/var/cloudbees/application-data/jenkins/workspace/Development/Security-Examples/Hello-World/Go/Build-Hello-World-Go-Watch-Revive@tmp/go'
11:56:47 GOPRIVATE=''
11:56:47 GOPROXY=''
11:56:47 GOROOT='/var/cloudbees/application-data/jenkins/workspace/Development/Security-Examples/Hello-World/Go/Build-Hello-World-Go-Watch-Revive@tmp/usr/local/go'
11:56:47 GOSUMDB=''
11:56:47 GOTMPDIR=''
11:56:47 GOTOOLCHAIN=''
11:56:47 GOTOOLDIR='/var/cloudbees/application-data/jenkins/workspace/Development/Security-Examples/Hello-World/Go/Build-Hello-World-Go-Watch-Revive@tmp/usr/local/go/pkg/tool/linux_amd64'
11:56:47 GOVCS=''
11:56:47 GOVERSION='go1.22.5'
11:56:47 GCCGO='gccgo'
11:56:47 GOAMD64='v1'
11:56:47 AR='ar'
11:56:47 CC='gcc'
11:56:47 CXX='g++'
11:56:47 CGO_ENABLED='0'
11:56:47 GOMOD='/var/cloudbees/application-data/jenkins/workspace/Development/Security-Examples/Hello-World/Go/Build-Hello-World-Go-Watch-Revive/go.mod'
11:56:47 GOWORK=''
11:56:47 CGO_CFLAGS='-O2 -g'
11:56:47 CGO_CPPFLAGS=''
11:56:47 CGO_CXXFLAGS='-O2 -g'
11:56:47 CGO_FFLAGS='-O2 -g'
11:56:47 CGO_LDFLAGS='-O2 -g'
11:56:47 PKG_CONFIG='pkg-config'
11:56:47 GOGCCFLAGS='-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1653639929=/tmp/go-build -gno-record-gcc-switches'

What did you do?

export GOPATH="$WORKSPACE_TMP/go"
export GOPROXY='https://proxy.golang.org,direct'
export GOROOT="$WORKSPACE_TMP/usr/local/go"
export PATH="$PATH:$WORKSPACE_TMP/bin:$GOPATH/bin"

mkdir -p "$WORKSPACE_TMP/bin"
mkdir -p "$GOROOT"
mkdir -p "$GOPATH"
curl -LO https://go.dev/dl/go1.23.2.linux-amd64.tar.gz
tar -C "$GOROOT" -xzf go1.23.2.linux-amd64.tar.gz

go install github.com/kisielk/[email protected]

What did you see happen?

Error
go: github.com/kisielk/[email protected]: GOPROXY list is not the empty string, but contains no entries

What did you expect to see?

No Error

[gabyhelp]

Related Issues and Documentation

• `go install` fails when `GOPROXY` is empty #62274 (closed)
• error gopath #66295 (closed)
• GOARCH=arm64 go build can't find imports #68007 (closed)
• cmd/go: locating GOROOT fails when the `go` command is run from the cross-compiled `bin` subdirectory #62119 (closed)
• x/tools/gopls: references doesn't work properly. #60676 (closed)
• go/build: Passes bad $GOROOT to `go list` subprocess #35056 (closed)
• affected/package: go env GOBIN #58851 (closed)
• missing dot in first path element when building from official golang Docker image #37396 (closed)
• cmd/go: go mod download breaks on 1.21.0 due to empty GOPROXY #61928 (closed)
• govulncheck-action: tar errors "Cannot open: File exists" #66888 (closed)

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

[aep-sunlife]

How come the Go 1.23.2 tarball produces a go env that claims GOVERSION "go1.22.5"?

By the way, GOSUMDB is also a blank string out of the box, which go install ... later complains about as well.

[seankhliao]

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

[aep-sunlife]

That's why I'm here; to analyze errors and potential bugs, not perform general discussions.

[ianlancetaylor]

You will get better and faster answers in a forum.

[aep-sunlife]

The root problem in this case seems to be untarring the Go archive directly into GOROOT, resulting in a corrupted directory structure .../go/go/...

Thereupon Go gets confused and ends up with a kinds of misbehaviors.

Changing the -C value to the parent of the GOROOT directory works much better.

[aep-sunlife]

You will get better and faster answers in a forum.

If that's the case then disable GitHub issues for this repository. No sense maintaining a forum that users are actively discouraged from using to troubleshoot errors.

[ianlancetaylor]

We use the issue tracker to track bug reports and proposed changes to the language and library.

We have tried to use it to help people with using Go, but we have found through experience that using a forum works better for the people who are having problems. That is why we wrote https://go.dev/wiki/Questions, and why we direct people there.

There are many millions of Go users, and there is a very small team of Go developers. The most effective way for users to get help is from other users. That is what forums are for.

Thanks for your interest in Go.