FS#48115 - [gdal] Incompatible with SQLite 3.10+

Attached to Project: Community Packages
Opened by Doug Newgard (Scimmia) - Wednesday, 10 February 2016, 14:53 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Monday, 22 February 2016, 19:56 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

gdal 2.0.1 and 2.0.2 will segfault when xCurrentTimeInt is called when using SQLite 3.10+.

Upstream report: https://trac.osgeo.org/gdal/ticket/6360
Patch: https://trac.osgeo.org/gdal/changeset/33411

This has been causing problems with QGIS: http://hub.qgis.org/issues/14123
This task depends upon

Closed by  Jaroslav Lichtblau (Dragonlord)
Monday, 22 February 2016, 19:56 GMT
Reason for closing:  Upstream
Additional comments about closing:  Let's assume it's all upstreams fault and run away. gdal 2.0.2-2 now in [community] and we'll see if Doug is right about latest gdal sorting this out.
Comment by Doug Newgard (Scimmia) - Wednesday, 17 February 2016, 00:00 GMT
SQLite 3.11 re-enabled xCurrentTime (see http://www.sqlite.org/changes.html), so it now works correctly with the current version of GDAL. I would guess that there will be a GDAL update before it's removed again, so this shouldn't be an issue.

Loading...