-
Notifications
You must be signed in to change notification settings - Fork 33
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
Can't build with v1.6.6 #14
Comments
I will first try to get the PR in (as a side note I was unable to reproduce after |
Strange. Maybe you have a leftover of a config file or nimble develop ? |
It might be best to try the new Nimble lock files to resolve these kinds of issues. @Clonkk you might be able to work around by removing any installed |
I did and still have the issue.
As long as nimble consider that Does |
It does not. There were some changes to how dependencies are installed in latest Nimble as well but I can't say whether this would change the semantics of the situation you describe (as I don't know myself). Indeed, it seems there isn't much we can do here other than hope that the two packages can both relax their package requirements, and lean more on the lock files to guarantee that |
That's a dependency resolution issue. Which is unfortunately a recurring issue for nimble. I hope after IC and arc/orc stabilization, the situation can be improved Relevant : |
Most likely, on this particular case, it seems the issue comes from : https://github.com/yyoncho/nim-json-rpc/blob/notif-changes/json_rpc.nimble using "requires asynctools". |
Note that solving this particular problem with local nimble develop puts in evidence another issue :
Which I assume is similar in nature |
@Clonkk I pushed yyoncho/nim-json-rpc@3888526 so hopefully this will fix the issue. |
I retried this morning; problem seems solved. |
I've firs tried
nimble install nimlangserver
and it fails.I then cloned this repo on the master branch and building (
nimble build
) the repo and it also fails.Looking at the path list :
This is caused because Nimble does not handle transitive dependencies and consider fork of a Nimble package as independent.
As you can see there is 2 asynctools package : the fork and the "nimble" one in the dependencies list and both are treated as separate.
The fork of asynctools need to be merged in the main nimble repository to be able to handle transitive dependencies AND/OR Nimble dependencies resolution should be fixed, specifically when using fork of nimble package.
You can work around this by modifying locally asynctools and using
nimble develop
but it shouldn't be considered as a practical solution because it would prevent the usage ofasynctools
as a nimble repo.The text was updated successfully, but these errors were encountered: