Arch Migrator

[regro-cf-autotick-bot]

This feedstock is being rebuilt as part of the aarch64/ppc64le migration.

Feel free to merge the PR if CI is all green, but please don't close it
without reaching out the the ARM migrators first at @conda-forge/arm-arch.

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

[loriab]

@conda-forge-admin, please rerender

[hmaarrfk]

I feel like you should bump the build number since the ci support files change so much

[loriab]

@mfherbst, I think this is ready for consideration. no rush

[hmaarrfk]

I feel like hte line:

- numpy >=1.14

might be interefering with our global pinnigns.

I would:

1. Manually copy in the numpy 2.0 migration file from https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/migrations/numpy2.yaml into the directory .ci_support/migrations
2. Remove the "greater than" constraint in the host and build section.
3. Add it to the run section

See more instructions (updated ones from)

conda-forge/conda-forge-pinning-feedstock#6301 (review)

[loriab]

@conda-forge-admin, please rerender

[loriab]

I feel like hte line:

- numpy >=1.14

might be interefering with our global pinnigns.

Done, thanks for the advice, @hmaarrfk. I'll have to look if there are other psi4 deps with numpy constraints, in case that's what's causing the persistent bot error at the np2 migration ( https://conda-forge.org/status/migration/?name=numpy2 -> bot-error -> psi4).

[mfherbst]

Looks good to me. Thanks @loriab and @hmaarrfk for your help ! I'll merge this in the next few days unless someone protests.

@mnottoli you agree ?

[mnottoli]

Looks good also to me. Thanks all for the help.