-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
libgit issues with Julia 1.6.5 h989b2f6_0 #166
Comments
This seems to work fine:
|
Ugh... I thought the libgit patch wasn't needed for the 1.6.x versions... We may want to actually solve this more properly later; I think we could work on constraining the exact version they're relying on upstream. I remember looking into it (you either apply the patch) or constrain libgit like libunwind, etc. |
Upstream is pinned at libgit2 version 1.1.0. |
See also JuliaLang/julia#42209 (libgit2 version 1.2) |
This comment has been minimized.
This comment has been minimized.
nvm sorry, it should take care of it, I think |
1.7.1 is pinned at the same version, and the patch does seem to work. |
Yep, sorry I wrote that without thinking! Will hide the comment :) |
Sorry to ping this old thread - I expanded the PySR unit tests to include conda-forge on macOS, and am seeing this issue here: https://github.com/MilesCranmer/PySR/actions/runs/3060750059/jobs/4939640457#step:5:155. Any idea why this is occuring? |
The fix is to unset the environment variable julia-feedstock/recipe/scripts/activate.sh Lines 20 to 22 in a203b65
I think you need to unpin Julia from 1.7.1. |
Awesome, thanks! Will unpin pysr now. Is it possible to backport it, just to generalize the solution to other versions? |
The main issue is that Julia's mbedtls doesn't understand conda-forge's openssl certificate format. |
There seem to be potential libgit2 issues with Julia 1.6.5 h989b2f6_0
The text was updated successfully, but these errors were encountered: