Skip to content
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

Failed to retrieve a list of dependencies: Cannot resolve parent of / #1

Open
scisci opened this issue Aug 25, 2016 · 1 comment
Open

Comments

@scisci
Copy link

scisci commented Aug 25, 2016

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.

@mattfarina
Copy link
Member

@scisci I can help explain what's happening here.

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:

  1. The Godeps.json file doesn't have the revision that the source is actually at. There is a mismatch.
  2. When the Godeps.json doesn't have a record for a needed package but something it's importing does.

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

No branches or pull requests

2 participants