Build with hdf5=1.0.5
xylar opened this issue · comments
The latest packages on conda-forge are build with hdf5=1.0.5, but cdat v8.1 and its dependencies are built with hdf5=1.0.4. Could a new build be made with hdf5=1.0.5 for compatibility with conda-forge?
@dnadeau4 can we do this?
The issue I had was netcdf 4.7 and other libraries (libcf, libcdms,...) I had to pin netcdf=4.6.2 Last time I tried to upgrade libnetcf to 4.7 some conda-forge libraries were still at 4.6.2, I can try again and see if I can make it work. Issues often arise on OSX, but not Linux due to the some version metadata.
@dnadeau4, I believe this is the official place to see what the current conda-forge pinnings are:
https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml
If you look there, they're still using libnetcdf 4.6.2:
https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml#L455
But hdf5=1.10.5:
https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml#L416
So I don't believe you need to update to libnetcdf 4.7 in order to use hdf5 1.10.5. conda-forge is not.
I would imagine it would make all of our lives easier if more cdat packages made their way to conda-forge. If you're interested in doing that and need another maintainer to help with the process, let me know. I'm vaguely aware that some packages are on conda-forge and others are not but I'm not quite clear on which and why.
@xylar we have recipe for all but vtk-cdat pkg takes too long to build and is killed by conda-forge... Hence we could never push it to conda-forge. And therefore all of our graphics are NOT on conda-forge. But this is not the issue here as cdms2 is on conda-forge.
@xylar I had to recompile CDMS2 2 weeks ago since conda-forge changed the gcc compiler to clang on OSX. The cdat/label/nightly channel has 1.10.5 for hdf5. I could try to make a point release on conda-forge. @doutriaux1 is this ok with you?
@doutriaux1, ah, that makes sense. I can see why vtk-cdat might be a problem beyond building -- it vendors a lot of other stuff from what I recall and conda-forge doesn't allow that. Thanks for the clarification.
cdms2 from conda-forge is working fine with hdf5=1.10.5. I'll try to figure out which package wasn't happy with that hdf5 version. I assume it was something in cdat/label/v81 but I didn't figure out for sure which.
I'm not sure if either of you did anything, but I am now able to build the environment I need with hdf5=1.10.5. Not sure what changed or what wasn't working before. But thank you both either way!