Rebuild for metis511

[regro-cf-autotick-bot]

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

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/6817418283, please use this URL for debugging.}

[conda-forge-webservices]

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) and found it was in an excellent condition.

[traversaro]

Hello everyone,
just a small warning on this migration: from METIS 5.1.0 to 5.1.1 the values of the enum moptions_et, including constants such as METIS_OPTION_NUMBERING (see KarypisLab/METIS#71 (comment)) have changed in backward incompatible way. So if this values are hardcoded in the code (as it happens for example for FORTRAN libraries), those values needs to be changed, as otherwise the wrong option is silently used. If instead the constants are used (for example in C/C++ code) the migration should be ok. See https://github.com/conda-forge/mumps-feedstock/blob/c524cb3c71686bee59d9b12df5d9d6ce20782ce4/recipe/mumps_support_only_metis_5_1_1.patch for example patch fixing this for MUMPS. Related issues:

• Large 2000x peformance regression from 5.1 to 5.2 KarypisLab/METIS#71
• Version 5.1.1 breaks downstream software metis-feedstock#35
• metis wrapper broken with metis 5.1.1 and 5.2.1  ralna/spral#133

[xylar]

@vijaysm, @iulian787, @gonuke and @scopatz, is there any reason not to merge this and migrate to Metis 5.1.1? Unless you are aware of places we will run into the issue that @traversaro mentions above, it seems like we should migrate.

[traversaro]

Just for full alignment, other feedstocks are experiencing problems with metis 5.1.1, even if we did not isolated the specific problems:

• Crash with metis 5.1.1 mumps-feedstock#106
• Rebuild for metis511 gtsam-feedstock#21

[vijaysm]

Sorry, I confused this with 5.2.x versions, where we had some build issues. Metis 5.2.x splits the GKlib into its own subrepository. This meant that -lGKlib had to be propagated separately to get linking working in some configurations.

We already use 5.1.0 without any issues. I think 5.1.1 upgrade may be fine if needed to simplify the recipe, though I can't find the change history for this version anywhere to confirm whether it would break anything on other architectures.

[xylar]

Maybe given that other packages are having trouble with metis 5.1.1 and we don't have anyone waiting on this migration downstream (https://conda-forge.org/status/#metis511), we can just put this in draft mode and ignore it?

[vijaysm]

Sounds good. My workstation has Metis 5.1.0 and it works well for all relevant usecases. I will try installing 5.1.1 to see if there are regressions, before we decide on this merge.

[traversaro]

I guess we can now close the PR, as the migration to metis 5.1.1 was halted due to upstream problems in metis 5.1.1, see conda-forge/mumps-feedstock#106, conda-forge/conda-forge-pinning-feedstock#5396 and conda-forge/conda-forge-pinning-feedstock#5397 . @minrk

[vijaysm]

Thanks for the update @traversaro

[xylar]

Thanks