-
Notifications
You must be signed in to change notification settings - Fork 0
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 install with nimble: nimterop versions #21
Comments
Line 12 in 2bfc46e
<= 0.6.12 . That's what gittyup needs as well.
|
How is it that the |
It looks like this issue: nim-lang/nimble#505 Log says both nimterop v0.6.12 and v0.6.13 are installed already but the dependency checker picks both versions and then dies at the end. I've not dabbled with the dependency code so cc @dom96. |
I guess one solution is to use Nimph; another is to use Nimble in localdeps mode so it has no redundant copies of nimterop. A third way might be to manually edit the requirements to remove any version other than 0.6.12. A fourth solution would be to remove nimterop 0.6.13 from your global nimble package directory. |
Yeah, this is a bug. Seems like simply picking the minimal version might help, but would need to take a look at the code again to know. |
I was able to complete installation using the fourth solution: Perhaps you should list in the README the external dependencies, for Ubuntu 20.04:
Now, even if golden binary has been created, I can't run it:
I'm also unable to regenerate it with I've tried bypassing the libgit2 library with |
This is a nimterop bug I forgot about - I'll get back to you on it. @disruptek are you okay with switching to static linking libgit2? -d:git2Static should avoid this issue. https://github.com/disruptek/golden/blob/master/src/golden.nim.cfg#L16 |
I'm okay with someone else using |
Trying to install golden with nimble, to use it with nim 1.4, raise an install error on nimterop versions:
I can't find which package requires nimterop 0.6.12 and why such a version restriction has been set.
The text was updated successfully, but these errors were encountered: