Fixed #32544 -- Confirmed support for GDAL 3.2 and GEOS 3.9.#14212
Fixed #32544 -- Confirmed support for GDAL 3.2 and GEOS 3.9.#14212felixxm merged 1 commit intodjango:mainfrom
Conversation
|
I deliberately mostly kept using |
|
Oh, and we should also discuss the backport to 3.2, as the only changes are in tests. |
|
@claudep Thanks for this patch 👍 I checked locally with GDAL 3.2.2 and GEOS 3.9.1 and still have some failures: DetailsMaybe it's some issue with my local configuration 🤔 . |
|
My tests were with GDAL 3.2.1 and GEOS 3.9.1. It may be that GDAL 3.2.2 introduced regressions. I'll see if I can investigate during the next days (but if someone beats me, would be fine :-). |
|
GDAL 3.1.4 and GEOS 3.9.1 configuration works for me with this patch. I will try to check GDAL 3.2.0 and 3.2.1 locally. |
|
I've checked many combinations and it looks that there is some breaking change or regression in GDAL 3.2.2:
|
|
Wow, great investigation! Should we report something to https://github.com/OSGeo/gdal/issues? |
I now have dozens of GDAL/GEOS versions 😄
I reported an issue, see OSGeo/gdal#3656. Unfortunately without many details 😞 |
|
I rebuilt GDAL 3.2.2 again and now everything work fine 🤕 Sorry for the noise.
|
carltongibson
left a comment
There was a problem hiding this comment.
we should also discuss the backport to 3.2, as the only changes are in tests.
That seems reasonable to me if you two are agreed. 👍
Thanks both. 🥇
No description provided.