-
-
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
Incompatibility between latest julia=1.7.1
and latest openlibm=0.8.0
on conda-forge
#169
Comments
Thanks. I was the one who pushed the 0.8.0 openlibm (and added arches there too). Should've paid attention. Should we do this pin more systematically somehow? I will make a quick fix for now. |
What's the actual error? |
Looks like failed env solving: https://github.com/ESMValGroup/ESMValTool/runs/4715592816?check_suite_focus=true |
|
Ah, yes, the ABI version changed in openlibm from 3 to 4. |
Is this something we should pursue more systematically, a la libunwind? Or should the quickfix suffice for now? |
Funny thing is... JuliaMath/openlibm#248 (comment) |
CC @mkitti |
@valeriupredoi this should be fixed. I will leave this open for now because we should pursue a more systematic solution with global pinning. However, it seems julia will drop openlibm pretty soon-ish. |
cheeers muchly for your work, guys! Please close when you think it's ready to be closed, I am happy on our side of things 🍺 |
I think @ngam is working on the global pinning now. I suppose we'll keep this open until that is complete. |
whatever works for you guys, I'm a happy camper now that our envs get sorted 😁 |
@valeriupredoi I am still concerned about this. I suppose it passed your tests because it's making a new environment. In my older environment, it is still broken even if I You should perhaps keep a strict pin on your end if you want to ensure your package works as expected for all users. |
new env:
|
old env even after
It basically taking this as more of a stable position for the current env. |
This is why we urgently need global pinning, I suppose... |
@wolfv @isuruf @jakirkham quick question about how mamba/conda resolves We had an issue yesterday where one dep (openlibm) slyly changed its abi number when it moved to cc @conda-forge/core |
Can you target the desired version directly? TLDR: repodata patch might be needed. |
Is it possible to just pull openlibm 0.8 for the moment? Is there anything that is actually using it? |
Can't really say, but with the CDN sync delays it will take a bit to show up for users. It might be as fast to just patch Julia packages here. |
This needs a repodata patch. We should avoid pulling deps and builds of big packages like these. |
Makes sense, thanks! Yes, the direct solution works. |
Thanks @beckermr, see pr: |
as @jaimergp points out conda (mamba) likes to go up in version numbers - that's why when you do an |
Given that JuliaMath/openlibm#248 says that the SONAME bump was a mistake, we can just make a symlink |
Definitely, but... like they did and decided it was the lesser of two evils to just go ahead with the mistake, we might as well follow their suit, otherwise, we will forget to disable the symlink, etc. |
hey guys, heads up that now Julia installation from conda-forge (the updated |
@SylvainCorlay just reported the same thing The errors all point to a segfault in curl, and curl 7.81 was released. |
Okay, gonna add curl <7.81 to repo patch now: conda-forge/conda-forge-repodata-patches-feedstock#208 |
More reports of same issue, from archlinux: JuliaLang/julia#43682 |
cheers muchly @ngam - apologies I didn't pick up on the version upping of |
LOL it's okay. They've been somewhat unfriendly (we discussed this a little bit here: conda-forge/mbedtls-feedstock#1), but we will figure things out soon. We are (in conda-forge/julia-feedstock) serious about having this work flawlessly. For now, we are playing catchup with issues emerging (libunwind, openlibm, curl, who know what's next tomorrow!), but hopefully soon we will figure out a more systematic approach. The ultimate problem isn't the people upstream per se, it is more their design choices of how julia is built and shipped. They ship julia with exact pins (and vendoring everything). I am quite outspoken and I don't mind speaking up repeatedly about this. This is really a losing strategy for julia and the open-source community at large: We all want julia to succeed and become a model for open-source collaboration; we don't want julia to become the next Matlab |
Hey, you've been extremely helpful. Please keep them coming and as @mkitti mentioned, we are going to be proactive about ensuring your work is tested by us before updating/merging. |
🤣 Keep up the good work, I'll try help as much as I can, even though that might just be poking you and complaining things are broken again 😁 |
Status update:
|
Morning guys, heads up that your latest fix in the |
See: * JuliaLang/Downloads.jl#172 * conda-forge/julia-feedstock#169 (comment) PR: 261417 Reported by: [email protected]
See: * JuliaLang/Downloads.jl#172 * conda-forge/julia-feedstock#169 (comment) PR: 261417 Reported by: [email protected]
@valeriupredoi and @ngam , I believe this issue can be closed since the above pull requests have been merged. Feel free to reopen if that is not the case. |
Hey guys, Happy New Year! Just a heads up that the latest Julia can not be installed in a conda env with deps from
conda-forge
unless one pinsopenlibm=0.7.0
(presumably a pin likeopenlibm<0.8
should work too) since the latestopenlibm
is now 0.8.0 as of 12 hours ago; see our issue on this matter ESMValGroup/ESMValTool#2450 Cheers 🍺The text was updated successfully, but these errors were encountered: