relate_bnr.sql

Paul Ramsey pramsey at cleverelephant.ca
Tue Aug 20 19:18:23 PDT 2024



> On Aug 20, 2024, at 6:01 PM, Imre Samu <pella.samu at gmail.com> wrote:
> 
> Paul Ramsey <pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca>> ( 2024. aug. 20., K, 21:39):
>> If we leave the stable branches alone, that will mean that anyone upgrading GEOS underneath postgis 3.4 and lower will end up with regression failures.
> 
> I also encountered this issue with the docker-postgis *-master images, 
> where the latest developer commit from GEOS ("main" branch) is being used.
> Currently, I'm using the GEOS "3.12" branch for this reason as a workaround.
> ( https://github.com/libgeos/geos/tree/3.12 ).
> 
> So, I would also appreciate some sort of solution, 

I think it probably makes sense to cherry pick the regression changes needed on main into some of the stable branches, basically not running the relate_bnr.sql tests if GEOS >= 3.13, and some small alterations to the two other tests that fail to make them version-agnostic.

+ifeq ($(shell expr "$(POSTGIS_GEOS_VERSION)" "<=" 31200),1)
+       TESTS += \
+               $(top_srcdir)/regress/core/relate_bnr
+endif

Once we have the last bug out of 3.13 I am going to bring those changes into main.

P

> although the problem is no longer critical with the workaround in place.
> 
> Currently, debian 'experimental' has already started using the geos 3.13.0~beta1-1~exp1 .
> https://packages.debian.org/experimental/source/geos
> 
> Imre

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20240820/c947de7e/attachment.htm>


More information about the postgis-devel mailing list