conda-forge / gdal-feedstock

A conda-smithy repository for gdal.
BSD 3-Clause "New" or "Revised" License
30 stars 63 forks source link

python 3.11 `libgdal-3.8.5-h35436ae_0 requires lerc >=4.0.0,<5.0a0` #911

Open Chrismarsh opened 7 months ago

Chrismarsh commented 7 months ago

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.11

Encountered problems while solving:
  - package libgdal-3.8.5-h35436ae_0 requires lerc >=4.0.0,<5.0a0, but none of the providers can be installed

Could not solve for environment specs
The following packages are incompatible
├─ libgdal >=3.8.5,<3.9.0a0  is installable and it requires
│  ├─ lerc >=4.0.0,<5.0a0 , which can be installed;
│  ├─ libdeflate >=1.20,<1.21.0a0 , which can be installed;
│  ├─ libexpat >=2.6.2,<3.0a0 , which requires
│  │  └─ expat 2.6.2.* , which can be installed;
│  ├─ libwebp-base >=1.3.2,<2.0a0 , which can be installed;
│  ├─ poppler >=24.3.0,<24.4.0a0 , which requires
│  │  └─ lcms2 >=2.16,<3.0a0 , which requires
│  │     └─ libtiff >=4.6.0,<4.7.0a0  with the potential options
│  │        ├─ libtiff 4.6.0, which can be installed;
│  │        ├─ libtiff 4.6.0 would require
│  │        │  └─ libdeflate >=1.19,<1.20.0a0 , which conflicts with any installable versions previously reported;
│  │        └─ libtiff 4.6.0 would require
│  │           └─ libdeflate >=1.18,<1.19.0a0 , which conflicts with any installable versions previously reported;
│  ├─ proj >=9.4.0,<9.4.1.0a0 , which can be installed;
│  ├─ xz >=5.2.6,<6.0a0 , which can be installed;
│  └─ zstd >=1.5.5,<1.6.0a0 , which can be installed;
├─ python >=3.11,<3.12.0a0  is requested and can be installed;

https://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

requirements:
  build:
    - cmake
    - ninja
    - make
    - {{ compiler('cxx') }}
  host:
    - python
    - scikit-build-core
    - cmake
    - pip
    - cgal-cpp
    - libboost-devel
    - libgdal
    - metis
  run:
    - python
    - vtk
    - numpy
    - scipy
    - matplotlib-base
    - cloudpickle
    - libgdal
    - gdal
    - metis
    - metis-python
    - mpi4py
    - natsort
    - libstdcxx-ng
    - libgcc-ng
    - gmp   

Environment info

On the build ci. I cannot figure out how to replicate this locally.
akrherz commented 7 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 :)

akrherz commented 7 months ago

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

Chrismarsh commented 7 months ago

What is the conda-forge way to work around this? libgdal<3.8.5?

akrherz commented 7 months ago

You could try that. I don't fully grasp the magic that is the conda/mamba dep solver and why it is hung up

Chrismarsh commented 7 months ago

That appears to have resolved it. Feels a bit janky, but I guess just wait until that vtk build is resolved?

akrherz commented 5 months ago

closing as I suspect this is resolved / stale, please reopen if not!

Chrismarsh commented 5 months ago

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