You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure what was going on here. I'm a Godep user, but wanted to see if I had out of date dependencies. I was only able to get a bunch of errors such as in the title as well as:
[ERROR] Error scanning github.com/xxxxx: open /Users/user/.glide/cache/src/xxxxx: no such file or directory
[ERROR] This error means the referenced package was not found.
[ERROR] Missing file or directory errors usually occur when multiple packages
[ERROR] share a common dependency and the first reference encountered by the scanner
[ERROR] sets the version to one that does not contain a subpackage needed required
[ERROR] by another package that uses the shared dependency. Try setting a
[ERROR] version in your glide.yaml that works for all packages that share this
[ERROR] dependency.
Not sure what to do.
The text was updated successfully, but these errors were encountered:
More than one of your dependencies is requesting a shared dependency. This is called diamond dependencies. On importing the data through the tree Glide attempts to learn the what versions of packages to use. Right now it uses the first version found, which would be the revision in your Godeps.json file.
Glide also walks through the import tree in the source.
This messages is saying the checked out version doesn't contain the needed package. This usually happens when an older version is checked out and something needs the newer version with the additional sub-package.
I've seen this happen in Godeps when:
The Godeps.json file doesn't have the revision that the source is actually at. There is a mismatch.
When the Godeps.json doesn't have a record for a needed package but something it's importing does.
Not sure what was going on here. I'm a Godep user, but wanted to see if I had out of date dependencies. I was only able to get a bunch of errors such as in the title as well as:
Not sure what to do.
The text was updated successfully, but these errors were encountered: