Skip to content
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

[gpuCI] Forward-merge branch-22.12 to branch-23.02 [skip gpuci] #807

Merged
merged 1 commit into from
Nov 17, 2022

Conversation

GPUtester
Copy link
Contributor

Forward-merge triggered by push to branch-22.12 that creates a PR to keep branch-23.02 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge.

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.

Authors:
  - AJ Schmidt (https://github.com/ajschmidt8)

Approvers:
  - Ray Douglass (https://github.com/raydouglass)
  - GALI PREM SAGAR (https://github.com/galipremsagar)
  - H. Thomson Comer (https://github.com/thomcom)

URL: #806
@GPUtester GPUtester requested a review from a team as a code owner November 17, 2022 22:12
@GPUtester GPUtester merged commit 29effaa into branch-23.02 Nov 17, 2022
@github-actions github-actions bot added the conda Related to conda and conda configuration label Nov 17, 2022
@GPUtester
Copy link
Contributor Author

SUCCESS - forward-merge complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conda Related to conda and conda configuration
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants