-
Notifications
You must be signed in to change notification settings - Fork 189
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
SAT resolution failure #1277
Comments
Araq
added a commit
that referenced
this issue
Oct 30, 2024
…en matched against another tag (#1279) * Tagged versions (i.e. #head) behaves like `any` except when matched against another tag * Updates changelog (#1276) * Updates changelog * Apply suggestions from code review --------- Co-authored-by: Andreas Rumpf <[email protected]> * bumps `setup-nim-action` (#1280) * bumps `setup-nim-action` * moves to stable (devel is not supported by `setup-nim-action@v2`) * adds `displayUsingUnderspecifiedVersionWarning` * fixes ci compile error --------- Co-authored-by: Andreas Rumpf <[email protected]>
I still have similar issue with 0.16.3. In my .nimble file, I have a dependency to libp2p:
When I run I have this error:
But when i run |
@2-towns fixed here: #1297 cc @arnetheduck |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the nim-libp2p repository, dependency resolution is failing when using the SAT dependency solver.
These are the scenarios:
nimble --solver:legacy install
nimble --solver:sat install
nimble install_pinned
(a custom mechanism that installs fixed versions from a.pinned
file into a localnimbledeps
directory, which is recreated each time it's run)a) When run with legacy (
nimble --solver:legacy install_pinned
), it works.b) When run with SAT (
nimble --solver:sat install_pinned
), it fails.c) Interestingly, if you first run it with legacy and then run
nimble --solver:sat check
, the check passes.At first I thought this was due to SAT not being able to resolve the dependencies in
libp2p.nimble
, but scenario3c
made me think that's not quite it.I'm not sure anymore if this happens because our dependencies are actually unsolvable or there's a situation SAT just can't handle. Any ideas?
The text was updated successfully, but these errors were encountered: