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

Rebuild for ipopt 3.14.17 #86

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update ipopt31417.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.


If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/12359750249 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@traversaro
Copy link
Contributor

Hello @bluescarni @darioizzo do you think we can merge this to let the ipopt31417 migration progress? Thanks!

@darioizzo
Copy link
Contributor

darioizzo commented Dec 18, 2024

Sure OK. Merging @traversaro . We do have issues lately with pybind11 intermodule dependency, so this merge will motivate me to also rebuild pygmo and pygmo_plugins_nonfree. Hopefully his will also solve (or at least clarify) esa/pagmo_plugins_nonfree#35 which indeed seems like and intermodule problem to me?

@darioizzo darioizzo merged commit 14a15d4 into conda-forge:main Dec 18, 2024
9 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the rebuild-ipopt31417-0-1_h268c37 branch December 18, 2024 09:55
@traversaro
Copy link
Contributor

For pybind11 you are probably affected by conda-forge/pybind11-feedstock#95 and conda-forge/pybind11-feedstock#96 . I personally dealt with that by pinning pybind11 to an earlier version (but that breaks numpy 2 support), and hopefully it will solved by a new pybind11 release.

@darioizzo
Copy link
Contributor

@traversaro I see, thanks for pointing this out, seems like a fundamental issue indeed. We thought it was solved by the virtual package pybind11-abi once and for all, but it seems like its resurfacing. I am not in the depth of conda machinery, but it is indeed a pity the implemented mechanism of ``pybind11-abi` seems to not be able to deal with this situation.

@traversaro
Copy link
Contributor

Yeah, the situation on pybind11 is a bit complicated at the moment, but hopefully it become much simpler once 2.14.0 is released. The pybind11-abi mechanism was valid, the problem is that it did not capture the fact that pybind11 considered each major release of gcc and clang as ABI-incompatible, and at some point also minor releases of MSVC as ABI-incompatible.

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 this pull request may close these issues.

4 participants