Skip to content
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

Backport cfitsio441 and numpy2 migrations #266

Open
duncanmmacleod opened this issue Sep 26, 2024 · 2 comments · May be fixed by #268
Open

Backport cfitsio441 and numpy2 migrations #266

duncanmmacleod opened this issue Sep 26, 2024 · 2 comments · May be fixed by #268
Labels
question Further information is requested

Comments

@duncanmmacleod
Copy link
Contributor

duncanmmacleod commented Sep 26, 2024

Comment:

Currently conda-forge-pinning pins downstream projects to root_base 6.32.0, while the latest release here is (ATOW) 6.32.2.

Rather than migrating to 6.32.2 (conda-forge/conda-forge-pinning-feedstock#6127) it might be faster to backport the cfitsio441 (#263) and numpy2 (#265) migrations to a maintenance branch for 6.32.0.

If that's reasonable, and someone from @conda-forge/root can create the maintenance branch, I am happy to cherry-pick those migrations into a new branch to build a new 6.32.0 package that includes them. If instead its actually cleaner/faster/less work to just start the migration to 6.32.2, I'm happy to wait for that to propagate.

Thanks.

@duncanmmacleod duncanmmacleod added the question Further information is requested label Sep 26, 2024
@duncanmmacleod duncanmmacleod linked a pull request Oct 4, 2024 that will close this issue
4 tasks
@duncanmmacleod
Copy link
Contributor Author

Ping @conda-forge/root, sorry to nag, but this issue is a blocker for me (aka the LIGO/Virgo/KAGRA collaborations).

@duncanmmacleod
Copy link
Contributor Author

Ping @conda-forge/root.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant