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: versions are not picked up from Gopkg.lock in a dependency #26418
Comments
Go modules only handles package A's legacy config (Gopkg.lock) now. |
So, what's the way to consume packages that are not |
Could you please also clarify "will / now": does it mean "we decided it's the right thing to do, so it's not likely to change" or "we don't have resources to make it work for transitive packages in time for 1.11, so that's how it is going to work in the release, but probably going to be changed later"? |
@misha-holahq Sorry for my poor English. Fixed. From rsc's commit message:
https://go-review.googlesource.com/c/vgo/+/120999 I hope I can help you. |
It's strange to have a Note that once you have it set up,
|
Add the missing dependencies to the As far as I can tell, |
What version of Go are you using (
go version
)?go version go1.10.3 darwin/amd64 vgo:2018-02-20.1
, vgo commit0f3e556044ecbd8a0805d098e52a743a1d0e3566
.Also tested on
go version devel +b59b42cee8 Tue Jul 17 10:07:18 2018 +0000 darwin/amd64
Does this issue reproduce with the latest release?
It used to work with vgo commit
0f3e556044ecbd8a0805d098e52a743a1d0e3566
. I have bisected the breakage. Broke in1b96834c2946460ab74b529df6b753fc0a03f628
.What operating system and processor architecture are you using (
go env
)?What did you do?
package A
go.mod
:package B
Gopkg.lock
:Old version of
vgo
honored the request for packageC v0.1.0. New versions ofvgo
andgo
from master ignore it and use latest one.Minimal reproducer: https://github.com/misha-holahq/test-vgo-importer
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: