Rebuild for python311#111
Conversation
…nda-forge-pinning 2023.05.02.09.44.55
|
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 ( I do have some suggestions for making it better though... For recipe:
Documentation on acceptable licenses can be found here. |
|
@dacase - Python 3.11 builds fail for 22.5 (we'll test with AT 23 shortly) due to: This is due to python/cpython#28968 (which moved some headers to a new location). Have you seen this, and is it fixed on v23, or do we need to file a report in the gitlab instance / patch it here? |
|
I have reports that there are more problems with python 3.11 and AmberTools23 than just the one about |
|
Got it! Let's re-run this migration to see what happens with AT23. |
|
I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/cf-scripts/actions/runs/4884911368 |
This PR has been triggered in an effort to update python311.
Notes and instructions for merging this PR:
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-rerunlabel 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 botin a PR comment to have theconda-forge-adminadd 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/4860633122, please use this URL for debugging.