gopkgs: go get failed
$ GO111MODULE=on go get github.com/uudashr/gopkgs/cmd/gopkgs@latest
go: finding github.com/uudashr/gopkgs/cmd/gopkgs latest
go get: github.com/uudashr/gopkgs/cmd/gopkgs@v0.0.0-20191024034442-58e9141cd7d6 requires
github.com/uudashr/gopkgs/v2@v2.1.0 requires
github.com/uudashr/gopkgs@v0.0.0: reading github.com/uudashr/gopkgs/go.mod at revision v0.0.0: unknown revision v0.0.0
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 56
- Comments: 34 (14 by maintainers)
Not sure if it is a workaround, but it seems to get rid of when deploy Go on VSCode, by changing from: GO111MODULE=on go get github.com/uudashr/gopkgs/cmd/gopkgs@latest to: GO111MODULE=on go get github.com/uudashr/gopkgs/cmd/gopkgs@v2
FYI this issue will come up anytime someone does a fresh install of VSCode (as I just did).
I can also reproduce this. Any known workarounds?
@BaptisteOue same applies to your case. Do not install it from the VSCode until the fix is merged, instead do this:
C:\Go\bin\go.exe get github.com/uudashr/gopkgs/v2/cmd/gopkgsto install the tool manuallyhttps://github.com/microsoft/vscode-go/pull/3057 should fix the issue for the VSCode users with the
github.com/uudashr/gopkgs/v2/cmd/gopkgspath. As for thev1path, we’ll probably have to introduce thego.modagain to the./cmd/gopkgspackage.@fearform for now just install it manually from the
v2path:go get github.com/uudashr/gopkgs/v2/cmd/gopkgsTry to run “go get -v github.com/uudashr/gopkgs/cmd/gopkgs” in folder C:\Go\bin using Command Prompt, and VCS should work properly.
cc @nezorflame
Oh… I think I know the reason. Try with
GOPROXY=direct go get ...@uudashr I think all that’s necessary to fix this is to tag a
v2.1.2release. Right now https://github.com/uudashr/gopkgs/blob/master/go.mod referencesv2.1.2, but that doesn’t exist.I’m getting the same error.
BTW the proper way to consume the
gopkgsnow that it has v2 is:go get github.com/uudashr/gopkgs/v2/cmd/gopkgs@latestorgo get github.com/uudashr/gopkgs/v2/cmd/gopkgs@masterfor master branch.Once we confirm the tag worked, it needs to be used this way in VSCode as well.