Skip to content
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

Pinning suitesparse #59

Closed
martinandersen opened this issue May 11, 2018 · 4 comments · Fixed by #1358
Closed

Pinning suitesparse #59

martinandersen opened this issue May 11, 2018 · 4 comments · Fixed by #1358

Comments

@martinandersen
Copy link

Raising this to see if suitesparse should be pinned globally.

re conda-forge/cvxopt-feedstock#19

@djsutherland
Copy link
Contributor

For the record, it's only broken compatibility on major versions, so the CB3 default behavior if you just list - suitesparse in run should be okay: https://abi-laboratory.pro/tracker/timeline/suitesparse/. But I guess there was an issue with the Mac install_name (conda-forge/cvxopt-feedstock#19 (comment))?

@jakirkham
Copy link
Member

Yeah it's a little more complicated. The SONAME is too specific. So we either need to patch it to be less specific or we need to pin suitesparse down to the patch version.

ref: conda-forge/suitesparse-feedstock#22 (comment)
ref: conda-forge/suitesparse-feedstock#23

@jakirkham
Copy link
Member

cc @minrk

@saraedum saraedum mentioned this issue May 22, 2018
1 task
@minrk
Copy link
Member

minrk commented Sep 24, 2019

conda-forge/suitesparse-feedstock#23 has been merged, so suitesparse shouldn't need pinning (at least not pin_run_as_build, which is the fix for what prompted the linked issues). If we want to use pinning to do coordinated upgrades, that's a different question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants