libabsl_cord.so.2301.0.0: cannot open shared object file #274
Comments
|
The channel column on your package list doesn't show conda-forge. I wonder if those packages are coming from defaults. |
|
It is not possible as my computer is in a private network, I'm only using a mirror to access conda-forge repository ( |
|
Surprisingly, rasterio doesn't depend on libaseil officialy even if libraries are linked against it. Only protobuf is listed by conda-tree: |
We don't know the status of that mirror and if it propagates things like repodatapatches. I believe you are in an unsupported side of things. With that said, I can reproduce that with our own packages and I'm not sure what may have caused it. Investigating... |
|
My GHA CI just hit this as well :/ An python 3.10 environmental diff between a job that worked 3 hours ago $ diff /tmp/good /tmp/bad
67a68
> gtest 1.14.0 h00ab1b0_1 conda-forge
85c86
< libabseil 20230125.3 cxx17_h59595ed_0 conda-forge
---
> libabseil 20230802.0 cxx17_h59595ed_3 conda-forge
88c89
< libarrow 13.0.0 h1ed0495_3_cpu conda-forge
---
> libarrow 13.0.0 h1935d02_4_cpu conda-forge
108,109c109,110
< libgoogle-cloud 2.12.0 h840a212_1 conda-forge
< libgrpc 1.56.2 h3905398_1 conda-forge
---
> libgoogle-cloud 2.12.0 h8d7e28b_2 conda-forge
> libgrpc 1.57.0 ha4d0f93_1 conda-forge
121c122
< libprotobuf 4.23.3 hd1fb520_1 conda-forge
---
> libprotobuf 4.23.4 hf27288f_5 conda-forge
155c156
< orc 1.9.0 h385abfd_1 conda-forge
---
> orc 1.9.0 h52d3b3c_2 conda-forge
173c174
< pyarrow 13.0.0 py310hf9e7431_3_cpu conda-forge
---
> pyarrow 13.0.0 py310hf9e7431_4_cpu conda-forge |
|
@hmaarrfk sorry for the random ping but maybe you know what may have changed in the underlying dependencies here? |
|
downgrading to |
That is why I asked Mark above. I wonder if we missed some pinning somewhere... |
|
The dep path appears to be rasterio -> libgdal -> tiledb -> libgoogle-cloud -> libgrpc , perhaps we need this specified within gdal? |
|
I'm hitting this reliably on conda-forge/isce2-feedstock#65 sorry i've been debugging it too. no clue as of yet. |
|
unfortunately, this will have to wait for @h-vetinari's input.... |
|
@hmaarrfk , perhaps this will be fixed by conda-forge/tiledb-feedstock#209 |
|
I already replied in a bunch of places for this, but yes, conda-forge/tiledb-feedstock#209 should fix this for the most part. Someone still has to go write a repodata patch for the old tiledb builds that don't have an libabseil-dependence, and will (probably...) continue to be wrongly considered by the solver for newer abseil, unless we patch in a run-dep for |
|
@rphel , can you verify that this issue has gone away now with tiledb builds 2 and 3 of version 2.16.3 now available? I am unable to locally reproduce anymore. |
|
Yes it works thanks! |
Solution to issue cannot be found in the documentation.
Issue
When building our software we encouter this error with rasterio (1.3.8-py310hd227816_0) linux libraries:
Both rasterio and GDAL libraries seem affected:
The version that is installed is:
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: