-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: no clear "go get" message when requested version doesn't match suffix #31498
Comments
Versions that start with We should provide a clear diagnostic message for this. |
This might be a duplicate of #30499. (Not entirely clear to me whether the problems occur under the same conditions.) |
@tbpg is working on this, but I'm not able to assign it to him. |
Change https://golang.org/cl/174180 mentions this issue: |
Change https://golang.org/cl/173721 mentions this issue: |
prometheus/prometheus#5356 (comment) is an interesting counter-point to this issue: it appears that some maintainers are already intentionally using mismatched module paths to avoid SemVer semantics for not-actually-SemVer repositories. That said, it seems like the pseudo-version we choose in that case should be based on the last |
Since CL 181881, we now print an error message like this:
Note that proxy.golang.org is still serving results based on go1.12 behavior (#32805), and we don't print this message for results received from the proxy. We probably should. |
That is tracked separately as #31428. |
I believe this is resolved. @firelizzard18, please let us know if this is still an issue for you using Go 1.13. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
go.mod:
What did you see instead?
I don't understand why
go get
is not respecting my tag. The correct tags exist.v1.6.1
works fine, butv2.0.0
andv2.1.0
don't work.The text was updated successfully, but these errors were encountered: