-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Update HDF5 ecosystem to 1.8.18 #71
Comments
II don't know much about it, but I thought updating https://github.com/conda-forge/conda-forge.github.io/blob/master/scripts/pin_the_slow_way.py would achieve the same result in a more automated fashion. cc @ocefpaf @jakirkham |
That would be the place to start. Yes the bot should do this, but it is broken of late. Still we should first send a PR to that script and only then PR the feedstocks after the pinning change has been accepted. |
@gillins Thanks for pointing that out - definitely looked for something like this but didn't see any traces of it in most feedstocks I sampled. Handling the upstream pin in conda-forge/conda-forge.github.io#394 |
Thank you for doing that @qwhelan and putting in the time to make all these PRs. It's definitely appreciated. |
Are we good to close this out? I think everything either got rebuilt with 1.8.18, got rebuilt with 1.10.1, or is simply lagging behind. |
After merging #68, I realized that almost all
conda-forge
packages have pinned their recipes to1.8.17|1.8.17.*
. Ashdf5
is cautious and checks that version numbers are the same for headers and shared objects, we'll need to update the pinned versions to allow a user to use1.8.18
.I identified all
conda-forge
packages usinghdf5
by checking out https://github.com/conda-forge/feedstocks, runninggit submodule init && git submodule update
, and then executing the following:I will be creating PRs for each library below and checking them off as they get merged:
1.8.*
rather than1.8.17|1.8.17.*
The text was updated successfully, but these errors were encountered: