It looks like the numpy 2.0 update was pushed to the gdal-feedstock
https://github.com/conda-forge/gdal-feedstock/pull/939 (looking like
GDAL must also build and test clean against Numpy 2.0 at this point too).
The error is the Conda builder complaining that it can't find Numpy
2.0 because our recipe doesn't use the Numpy 2.0 release candidate
channel. I think something is busted by this change to the recipe but
I have not had time to investigate it.
As suggested in the comment of #939, attempting
https://github.com/rouault/gdal/commit/1000cfaa950a18bd14b0c72109439cad58c789d5
My understanding is that the addition of this channel should only be a
build requirement, and not impose to add this channel when using the
generated package given than building against numpy 2.0 also yields
binaries that are compatible with the oldest supported numpy 1.x
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
