This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1k
Trouble with recursive constraints #1254
Comments
We have since fixed this issue with our repo layout, but I made a couple of repos that experience a similar issue during dependency solving: https://github.com/jrick/dep1254a-c I am unable to
|
hi! seems like this might be the same underlying issue as #1131? ("recursive" threw me off when i initially read this - "circular/cyclic" is the way i think of it) |
Yeah, cyclic is the correct term. Somehow that escaped me when I made this issue and didn't think to search for it. Closing since it's a known/duplicate issue |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This may fall under the category of "working as intended, fix your repo layout" and we certainly want to fix it in the future, but at the moment two of our repos have a recursive dependency on each other, and both use the master branch as the constraint for the other. This is causing issues when running dep ensure after modifying the manifest or running ensure -update at any time. Just looking for advice on whether this is considered a bug, if a workaround is possible, or if we need to change the repo layout.
What version of
dep
are you using (dep version
)?Tested with 0.3.1 and current master (d10af5e).
What
dep
command did you run?What did you expect to see?
Before the switch to dep, we used glide, and glide had no issues with the recursive repo layout and each project depending on master. I think this is due to dep being stricter about ensuring that all constraints can be satisfied.
I also tried using an override for the dcrrpcclient repo to force dep to not solve the version, but it still errored during solving.
The text was updated successfully, but these errors were encountered: