-
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: 'go get cloud.google.com/go@master' chooses a v0.0.0- pseudo-version #34266
Comments
However, the following does:
|
Possibly related to #34092, in that both seem to be symptoms of incomplete |
This is looking like another JGit bug to me: fetches from (The repo for
|
I have filed a Google-internal bug to track the issue in the |
@gopherbot, please backport to Go 1.13. This can cause errors in pseudo-version resolution, and the workarounds are not at all obvious. |
Backport issue(s) opened: #34477 (for 1.13). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
The workaround, in this case, is to pass |
Change https://golang.org/cl/196961 mentions this issue: |
Change https://golang.org/cl/197060 mentions this issue: |
…d an apparent bug in 'git fetch --unshallow' When 'git fetch' is passed the '--unshallow' flag, it assumes that the local and remote refs are equal.¹ However, we were fetching an expanded set of refs explicitly in the same command, violating that assumption. Now we first expand the set of refs, then unshallow the repo in a separate fetch. Empirically, this seems to work, whereas the opposite order does not. ¹https://github.com/git/git/blob/4c86140027f4a0d2caaa3ab4bd8bfc5ce3c11c8a/transport.c#L1303-L1309 Updates #34266 Fixes #34477 Change-Id: Ie97eb7c1223f944003a1e31d0ec9e69aad0efc0d Reviewed-on: https://go-review.googlesource.com/c/go/+/196961 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Jay Conrod <jayconrod@google.com> (cherry picked from commit 1804bba) Reviewed-on: https://go-review.googlesource.com/c/go/+/197060
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?
It works.
What did you see instead?
It provides a
go get: inconsistent versions
error.The text was updated successfully, but these errors were encountered: