Closed looooo closed 6 years ago
That's what PR ( https://github.com/conda-forge/vtk-feedstock/pull/56 ) should help us solve. It just ran into issues last time. Think there were some recent changes to the pinnings, which would be worth retrying. To try and minimize impact on others given the CI resources VTK uses. Will try to do this in the evening today.
So PR ( https://github.com/conda-forge/vtk-feedstock/pull/56 ) is refreshed. It's lagging a bit on the hdf5
pinning (would be 1.10.1
instead of 1.10.2
), but so is the whole stack, which is part of the reason it will lag (libnetcdf
needs 1.10.1
ATM). The rest are current.
ah good idea. I didn't know manual pinning overwrites the conda-forge-pinning.
Yeah, should be careful with it as things can go stale or get unmaintainable that way, but for now that seemed like the path of least resistance for vtk
and its use of hdf5
. There's a bunch of other tricks one can use. This doc page is probably the most useful in this regard.
conda-forge pinnings updated hdf5. Please update this recipe to use the same version.