-
Notifications
You must be signed in to change notification settings - Fork 541
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
Unable to generate glide.lock when testImport is being used #597
Comments
I can confirm this. I am using the latest master (because no easy way to install binaries on windows). glide.yaml
log:
|
Neither of these two above yaml files produce an error for me with the current release of glide (0.12.3); however, I ran into a very similar problem. I'm not sure if this is the entire problem or not, but I think what is happening is that:
I think common packages are almost certain to cause this problem; my conflict was on |
Ran into the same problem. |
I ran into the same problem. It's interesting. |
I think the |
I strongly disagree |
@arekkas well, "best solution" might have been a bad expression of what I meant. Let me rephrase to "easiest workaround". |
Not having a version constraint doesn't work either:
resulting in the following error
|
This prevents the issue described in Masterminds/glide#597
I'm trying to move my libs test deps out of
import
and intotestImport
, so that my lib doesn't impose constraints on my users test dependencies.I've updated my
glide.yaml
to move the test deps intotestImport
:But when I run
glide up
I get the errorFailed to generate lock file: Generating lock produced conflicting versions of github.com/golang/mock. import (), testImport (master)
:The version of glide at hand is
0.12.0
:And there is a branch to reproduce this here, just run this:
Is there a way to dump more info about the error?
The text was updated successfully, but these errors were encountered: