Open Chrismarsh opened 5 months ago
Thanks, my initial guess is that proj=9.4
is the problem and wow, I see the conda-forge status page has been greatly improved! Anyway, I'll look more into this once the eclipse ends :)
vtk hasn't been rebuilt for proj 9.4 yet conda-forge/vtk-feedstock/pull/322, so gdal=3.8.5 (wants proj=9.4) won't work with vtk
What is the conda-forge way to work around this? libgdal<3.8.5
?
You could try that. I don't fully grasp the magic that is the conda/mamba dep solver and why it is hung up
That appears to have resolved it. Feels a bit janky, but I guess just wait until that vtk build is resolved?
closing as I suspect this is resolved / stale, please reopen if not!
Something still seems strange. I tried to remove the version pin, and the build once again failed. I don't have a great handle on what conda is trying to do -- some very old API breaking GDAL versions are being tested which suggests it's super busted trying to resolve this. I've attached an arbitrary log from the CI log.txt
Solution to issue cannot be found in the documentation.
Issue
I'm trying to build against
libgdal
, (conda-forge/staged-recipes/pull/25976) however I am getting this error when the CI uses python 3.11https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=911643&view=logs&j=6f142865-96c3-535c-b7ea-873d86b887bd&t=22b0682d-ab9e-55d7-9c79-49f3c3ba4823&l=1055
I'm not sure how long that CI will remain so the log is attached as a file
log.txt
Installed packages
Environment info