Skip to content
This repository has been archived by the owner on Feb 26, 2019. It is now read-only.

inconsistent definition during import in godep go #10

Closed
kr opened this issue Oct 9, 2013 · 1 comment
Closed

inconsistent definition during import in godep go #10

kr opened this issue Oct 9, 2013 · 1 comment
Labels

Comments

@kr
Copy link
Member

kr commented Oct 9, 2013

Errors of the form

inconsistent definition for type ssh.CryptoConfig during import

occasionally happen when using godep.

Speculate the cause is switching between two sets of dependencies,
with one intermediate package S sharing a common version but using
two different versions of transitive dependency T:

Package P's Godeps:

P
1 S
2 T

Package Q's Godeps:

Q
1 S
3 T

where S depends on T, and P and Q may or may not directly depend on T.
Running godep go build in P causes T to build with the current timestamp.
Subsequently running godep go build in Q does not rebuild S, but is using
a different version of T. So Q and S see different, incompatible versions
of the symbols defined in T, and the program cannot link.

@kr kr mentioned this issue Oct 9, 2013
@freeformz
Copy link

I don't think this is still an issue. Closing for now. Please re-open if it is and I am wrong. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants