Skip to content
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' chooses a v0.0.0- pseudo-version [1.13 backport] #34477

gopherbot opened this issue Sep 23, 2019 · 2 comments


Copy link

@gopherbot gopherbot commented Sep 23, 2019

@bcmills requested issue #34266 to be considered for backport to the next 1.13 minor release.

@gopherbot, please backport to Go 1.13. This can cause errors in pseudo-version resolution, and the workarounds are not at all obvious.


This comment has been minimized.

Copy link

@gopherbot gopherbot commented Sep 24, 2019

Change mentions this issue: [release-branch.go1.13] cmd/go/internal/modfetch/codehost: work around an apparent bug in 'git fetch --unshallow'


This comment has been minimized.

Copy link

@gopherbot gopherbot commented Sep 25, 2019

Closed by merging fb86bbb to release-branch.go1.13.

gopherbot pushed a commit that referenced this issue Sep 25, 2019
…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

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.


Updates #34266
Fixes #34477

Change-Id: Ie97eb7c1223f944003a1e31d0ec9e69aad0efc0d
Run-TryBot: Bryan C. Mills <>
TryBot-Result: Gobot Gobot <>
Reviewed-by: Jay Conrod <>
(cherry picked from commit 1804bba)
@gopherbot gopherbot closed this Sep 25, 2019
@bcmills bcmills modified the milestones: Go1.13.1, Go1.13.2 Sep 25, 2019
@katiehockman katiehockman modified the milestones: Go1.13.2, Go1.13.3 Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.