-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: get: can't query version "patch" of module X: no existing version is required #49111
Comments
The errors look weird (those aren't module) |
|
I get the same thing on go master. |
Is something interfering with access to the proxy? Can you try GOMODCACHE=$(mktemp -d -t gomodcache.XXXX) GOPROXY=direct go get -u=patch -d -v and GOMODCACHE=$(mktemp -d -t gomodcache.XXXX) go get -u=patch -d -v |
|
|
do you have |
No. My hunch is this has to do with some bad versioning/tagging, possibly in mattn/go-sqlite. Can you reproduce it with anacrolix/torrent on your machine? |
I can't reproduce the errors you see when you're using a proxy. I see 2 different problems here
|
With just |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Closing this is a mistake @gopherbot, @seankhliao, thanks. |
This problem persists with go1.19rc1. |
Reproduce by checking out github.com/anacrolix/torrent or github.com/anacrolix/dht. Run with the default GOPROXY ( |
I confirm I've this Go proxy bug on on my local Ubuntu, with a VPN usage. $ go mod tidy
denis@L560:~/huma/compose-operator$ go get -u=patch k8s.io/api
go: k8s.io/api: can't query version "patch" of module k8s.io: no existing version is required
denis@L560:~/huma/compose-operator$ GOPROXY=direct go get -u=patch k8s.io/api
go: downloading k8s.io/api v0.25.13
go: downloading k8s.io/apimachinery v0.25.13
go: upgraded k8s.io/api v0.25.11 => v0.25.13
go: upgraded k8s.io/apimachinery v0.25.11 => v0.25.13
denis@L560:~/huma/compose-operator$ go version
go version go1.20.5 linux/amd6 |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes I think this is the latest release.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Ran
go get -u=patch
in any of my repos (anacrolix/torrent and anacrolix/dht for example).What did you expect to see?
Some noise about modules being updated to more recent patch releases.
What did you see instead?
The text was updated successfully, but these errors were encountered: