-
-
Notifications
You must be signed in to change notification settings - Fork 6
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 python311 #19
Rebuild for python311 #19
Conversation
…nda-forge-pinning 2022.10.29.17.19.28
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 ( |
Interesting. We just rebuilt |
@conda-forge-admin, please restart CI |
@conda-forge-admin, please re-render |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/pycuda-feedstock/actions/runs/3364474214. |
@conda-forge-admin, please re-render |
…nda-forge-pinning 2022.10.31.14.40.35
That doesn't seem to help. The particular error shown in CI currently is fixed in PR ( boostorg/python#328 ), which has been included in Boost since 1.76.0. In CI we are building with Boost 1.78.0 (so should already have that fix). However, on closer inspection, it seems these headers are coming from pycuda itself? In particular it looks like there is some kind of Boost.Python vendoring. This vendored copy of Boost.Python would need to be updated. Edit: Likely am missing context. Following up here ( inducer/pycuda#359 (comment) ). |
Ah thank you Isuru! 🙏 Figured there was something I wasn't understanding 😅 |
Think the naming structure expected by |
Thanks Isuru! 🙏 Looks like that found the library 🎉 Appears that |
Superseded by #20. |
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
We still need this for the migrator, which appears to be missing from |
Hmm...unfortunately the bot thinks this is done even though it is not. Let's try refreshing... @conda-forge-admin, please re-render |
…nda-forge-pinning 2022.11.21.19.57.06
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 ( |
@conda-forge-admin, please re-render |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/pycuda-feedstock/actions/runs/3520202249. |
Ok have tidied this up. Should be ready for review 🙂 |
LGTM, thanks! And sorry I closed this prematurely. |
All good. Thanks for all the fixes and review! 🙏 |
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-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 theconda-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/autotick-bot/actions/runs/3353156433, please use this URL for debugging.