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
go 1.11.4 does not seem to look into the vendor directory #29670
Comments
See https://github.com/golang/go/wiki/Modules#how-do-i-use-vendoring-with-modules-is-vendoring-going-away, in particular |
Please include a complete (and ideally minimal) source tree that reproduces the problem. |
@bcmills I do not think it's reasonable to require a minimal source code tree here, before there are any known steps of troubleshooting the issue (in fact, the troubleshooting steps is all I'm asking here for), all coupled with confusing/contradictory/outdated documentation of what's even supposed to happen here. All I did was install Go with
|
I'm sorry, but without knowing at least the directory structure of the code in question, we have no way to diagnose it: we don't know what package you are building, where the relevant https://golang.org/cmd/go/#hdr-Vendor_Directories describes the expected directory structure. You might be able to use |
I am not surprised that |
This issue stops being reproducible when Just as an example, searching for |
Given that you have a workaround, that the problem is only reproducible when working outside of That said, if someone wants to send a fix for 1.13 I'd be glad to review it. |
Are you saying it's normally supposed to work outside of I haven't tried reproducing it, but I don't see how my project would be different from any other one, so, I don't imagine you'd have any issues reproducing this. |
#14566 — the issue is closed, the follow-to issue is closed as well, giving you the impression it should all work nowadays years later, yet the problem still persists. There's just too much indirection for all of this, and documentation is clearly inadequate on this simple matter. |
The long-term resolution of #14566 is to use module mode when outside of In module mode (with Go 1.11.4 or later), If you find that that is not the case, please file a separate issue. |
Looking more closely, this issue seems to be a near-exact duplicate of #14566. Closing as such. As noted above, there are at least two possible workarounds: use |
@bcmills can you explain what you're trying to say?
|
The other bug was invalid. The solution there was to use modules. Since you don't seem to use modules, and are trying to build outside GOPATH, the same solution applies. Either build inside GOPATH, or use modules.
Read Bryan's replies carefully - that only makes a difference if you're building a module. If you're having issues getting set up to use modules, try asking for help in the #modules channel on gophers.slack.com. On the other hand, if you think you've found a bug, open an issue with complete instructions on how to reproduce it. Like Bryan said earlier, we need a full program and full instructions on what to do to reproduce the bug. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Running the latest release direct from a golang.org download.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
go build | & head -4
What did you expect to see?
Nothing — expected the build to complete successfully.
What did you see instead?
Issue
The issue I'm having is that not only is the
vendor
directory seemingly completely ignored (at least for this specific project, as per the error message), but that the error message seems to indicate that it's not even being looked at. I am not sure of the proper way to debug this, or how to troubleshoot this further. Thevendor
directory comes straight as part of a pristinegit clone
of a production package (that contains this vendor directory directly), and nothing in its path is a symlink.The text was updated successfully, but these errors were encountered: