GEOS version parsing fails if it has a trailing hash

[vonabarak]

Importing some classes (e.g. from django.contrib.gis.db.backends.base.features import BaseSpatialFeatures) using libgeos.py causes GEOSException('Could not parse version info string "%s"' % ver) django.contrib.gis.geos.error.GEOSException: Could not parse version info string "3.6.2-CAPI-1.10.2 4d2925d6"
I have been investigated this problem a bit. The reason is probably wrong version_regex in line 182 of libgeos.py
Exactly part corresponding to parse commit id (or whatever means " 4d2925d6" in version_string)

Use django 1.11 on freebsd 11

[Tim Graham]

​PR

[Hisham waleed karam]

the same error here

[yardensachs]

4d2925d6 is the commit for 3.6.2 tagged on:
​https://github.com/OSGeo/geos/tree/4d2925d6e0c758742a178053132eef02cd8374d2

So it looks like the commit hash was added to the version string.

And it looks like this is the commit that changed the version:
​https://github.com/OSGeo/geos/commit/cc5e205e5b4c7d4ee567bf39a548e65ecf51dd0e
More specifically:
​https://github.com/OSGeo/geos/commit/cc5e205e5b4c7d4ee567bf39a548e65ecf51dd0e#diff-8dd96440c9832c59176dcaa7c346b982

Hope this helps.

[Tim Graham]

I guess we should fix this on 1.11.x so we don't block the use of newer versions of GEOS there. ​PR for stable/1.11.x

[Tim Graham <timograham@…>]

In 78c155c:

Fixed #28441 -- Fixed GEOS version parsing with a commit hash at the end.

[Tim Graham <timograham@…>]

In a49764dd:

[1.11.x] Fixed #28441 -- Fixed GEOS version parsing with a commit hash at the end.

A less invasive backport of 78c155cf2e5a27fd2db18c2d46953b1b0fdba829
from master

[Johannes Maron]

Is this scheduled to be released soon?

If anyone has this issue on macOS and does not know how to solve it, this should do the trick:

brew switch geos 3.6.1

[Tim Graham]

Bug fix releases happen monthly, usually on the first of the month.

[will]

I met this kind of problem in Mac OS 10.12.6, django version 1.11.4.
My geos version is 3.6.2. I installed the plugins using brew.

[yardensachs]

This was fixed in 1.11.5 (which will be released this week).

[Rudolph Froger]

Please also fix this in Django 1.8.

[Simon Charette]

Rudolph, please take the time to read our ​backporting policy to understand why this wasn't backported to 1.8 before re-opening a closed ticket.

At this point, and when this ticket was reported as well, ​only security fixes and data loss bug qualify for a 1.8 backport.

[Nikolas Nyby]

I'm running into this problem in Django 1.11.25, Debian testing/bullseye:

  File "/home/nik/src/d/blackrock/ve/lib/python3.7/site-packages/django/contrib/gis/geos/libgeos.py", line 196, in geos_version
_info
    raise GEOSException('Could not parse version info string "%s"' % ver)
django.contrib.gis.geos.error.GEOSException: Could not parse version info string "3.8.0-CAPI-1.13.1 "

[Mariusz Felisiak]

Nikolas, thanks for this report, however Django 1.11 doesn't receive bugfixes anymore (it is in extended support).

[Kirill Malyshev]

Replying to Nikolas Nyby:

Had same issue today. Resolved by downgrading geos to 3.7.2 and gdal to 3.0.1.