<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<blockquote type="cite"
cite="mid:F1BE99EB-0EC7-4A54-88D4-CC0C9D2FC11D@hobu.co">
<div>It looks like the numpy 2.0 update was pushed to the
gdal-feedstock <a
href="https://github.com/conda-forge/gdal-feedstock/pull/939"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/conda-forge/gdal-feedstock/pull/939</a> (looking
like GDAL must also build and test clean against Numpy 2.0 at
this point too).</div>
<div><br>
</div>
<div>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.</div>
</blockquote>
<p>As suggested in the comment of #939, attempting
<a class="moz-txt-link-freetext" href="https://github.com/rouault/gdal/commit/1000cfaa950a18bd14b0c72109439cad58c789d5">https://github.com/rouault/gdal/commit/1000cfaa950a18bd14b0c72109439cad58c789d5</a></p>
<p>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<br>
</p>
<p>Even</p>
<span style="white-space: pre-wrap">
</span>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>