-
-
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
Adopt cfep 25 #48
Adopt cfep 25 #48
Conversation
@conda-forge-admin, please rerender |
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/meta.yaml:
|
fceec0c
to
27b7170
Compare
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 ( |
Hm, why is this expanding the CI matrix to so many Python-specific jobs? It's still noarch:python after all 🤔 Could this be a |
Looks like 3.9 is still being built. |
oh, I think that was my fault for rewriting some git history and force pushing rapidly :O lemme trigger one more build and I think things should clear up 🤞 |
6599025
to
317f376
Compare
@conda-forge-admin, please rerender |
66d4c29
to
85efadb
Compare
@conda-forge-admin, please rerender |
ok so, I think this might be a bug with conda-smithy. When I test out re-rendering locally after modifying the recipe to not be a split package things work as expected. For example, just build one of the packages (not as a split package)
run the rerender
the generated
|
Try using jinja2 to set python_min to 3.10 instead of the conda build config. |
I think the issue is that on the first pass, conda build does not use the python_min variable in the conda build config. I think the next version of conda build will have this fixed due to a PR I sent. However, in the mean time jinja2 should fix it. |
Ah I see, gotcha! Thanks for taking a look 👀 |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.11.12.14.24.54
Hrmmm that didn't work. I'll take a closer look tomorrow. |
@conda-forge-admin rerender |
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/conda-forge-webservices/actions/runs/11809133888. |
So as far as I can tell, this regex for finding variants is wrong: https://github.com/conda/conda-build/blob/main/conda_build/variants.py#L752 For It also does not match |
This PR appears to have broken matches to pin_compatible statements: conda/conda-build#2838 |
This PR appears to fix things: conda/conda-build#5535 |
…dev3+g6789a15a, and conda-forge-pinning 2024.11.12.14.24.54
wow @beckermr thanks for looking into this! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ref: https://github.com/conda-forge/cfep/blob/main/cfep-25.md
This pr:
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)