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 -u for package with submodule vendor: package <VENDOR PACKAGE>: <GIT DIR> exists but is not a directory #17522
Comments
@rsc since you just fixed the other half of this |
Just ran into this. Is there a workaround, since it looks like 1.8 was released w/o a fix? |
@akerl, Ended up getting around this for one of my repositories that stopped working on upgrading to 1.8 by using git submodules to vendor dependencies and avoiding |
CL https://golang.org/cl/49391 mentions this issue. |
I'm seeing something very similar too - not sure I quite understand:
note it works fine without -u:
istio.io/fortio maps to github.com/istio/fortio ps: same with go 1.10rc2:
|
after fixing the vanity url to add something for vendor (which shouldn't be needed... imo):
I now get
|
To avoid package istio.io/fortio/vendor/golang.org/x/net/context: istio.io/fortio is a custom import path for https://github.com/istio/fortio, but /go/src/istio.io/fortio/vendor is checked out from https://github.com/istio-releases/fortio-vendor.git But then one gets golang/go#17522 (comment)
and with 1.10rc2, different error:
|
I tried adding a branch to my submodule but exact same error
|
To avoid package istio.io/fortio/vendor/golang.org/x/net/context: istio.io/fortio is a custom import path for https://github.com/istio/fortio, but /go/src/istio.io/fortio/vendor is checked out from https://github.com/istio-releases/fortio-vendor.git But then one gets golang/go#17522 (comment)
cc @bradfitz any chance this can be fixed before 1.10 goes final, or at least in 1.11 ? |
@ldemailly, it's way too late for Go 1.10. Go 1.10 froze over 3 months ago. It's marked for Go 1.11, but it was also marked for Go 1.8, so.... we'll see. |
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
What did you see instead?
No problem with 9a97c3b patch it self, but not completely. In
src/cmd/go/get.go
go/src/cmd/go/get.go
Lines 419 to 423 in 9a97c3b
Should it must to be a directory for
meta
?The text was updated successfully, but these errors were encountered: