-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set max version pin for gdal
#806
Conversation
This PR sets a maximum version pin for `gdal`. Recently, `gdal` version `3.6.0` was released, which has a different version number for the `libgdal` shared object (`libgdal.so.32` vs. `libgdal.so.31`). Setting the max pin here will ensure that we use a consistent `libgdal` shared object version for building and at runtime. This should solve the `ImportError: libgdal.so.32: cannot open shared object file: No such file or directory` errors that have been popping up in recent Jenkins logs.
@gpucitbot merge |
Note that there is a interaction with tensorflow and gdal. We had a past PR (can't find, on mobile now) that set / pinned our gdal version in the conda recipe to avoid conflicts with AI packages. |
Good to know. I think we should be okay here though since we're setting a max pin. The max pin will just exclude the |
@gpucibot merge |
(there was a typo in Thomson's merge comment) |
Description
This PR sets a maximum version pin for
gdal
. Recently,gdal
version3.6.0
was released, which has a different version number for thelibgdal
shared object (libgdal.so.32
vs.libgdal.so.31
).Setting the max pin here will ensure that we use a consistent
libgdal
shared object version for building and at runtime.This should solve the
ImportError: libgdal.so.32: cannot open shared object file: No such file or directory
errors that have been popping up in recent Jenkins logs.Checklist