fix: resolve GDAL 3.12 API compatibility issues #1927
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: I'm not sure this is the best fix, but currently "make build" doesn't work, so we should figure out something :).
This fixes build failures caused by GDAL 3.12.0 migrating to Debian testing on November 15, 2025. The migration introduced breaking API changes in GetGeoTransform/SetGeoTransform signatures that are incompatible with Python GDAL 3.11.3 bindings.
Changes:
Root cause: Debian testing was pinned to get "3.10.x" but is a rolling target. When GDAL 3.12 migrated to testing, builds broke due to C++ API changes (double* -> GDALGeoTransform&) that pip-compiled bindings don't support.