Re: transition: geos (spatialite->postgis->gdal->spatialite circular dependency)
I'm having an error when I try to load spatialite extension in sqlite
under Sid :
SQLite version 220.127.116.11 2015-07-29 20:00:57
Enter ".help" for usage hints.
Connected to a transient in-memory database.
sqlite> select load_extension("/usr/lib/x86_64-linux-gnu/libspatialite.so.7");
Error: /usr/lib/x86_64-linux-gnu/libspatialite.so.7: undefined symbol:
Before filing a bug, might that be a temporary side effect of this transition ?
I'm using sqlite3 18.104.22.168-1 and libspatialite7 4.3.0-3.
2015-08-29 18:23 GMT+02:00 Sebastiaan Couwenberg <firstname.lastname@example.org>:
> On 27-08-15 18:12, Sebastiaan Couwenberg wrote:
>> After the buildds have completed these builds, the follow uploads will
>> be made:
>> * spatialite (4.3.0-3)
>> Reinstates liblwgeom-dev dependency to fix the regression
>> * gdal (1.11.2+dfsg-3)
>> Requires libspatialite-dev (>= 4.3.0-3~)
>> * postgis (2.1.8+dfsg-4)
>> Requires libgdal-dev (>= 1.11.2+dfsg-3~)
>> After that the rest of geos rdeps can be rebuild as usual.
> spatialite (4.3.0-3), gdal (1.11.2+dfsg-3) & postgis (2.1.8+dfsg-4) have
> been uploaded to unstable.
> Only the armel builds for gdal & postgis are still missing because gdal
> is stuck in Uploaded status for over 10 hours.
> Most other packages affected by the geos transition have also been
> uploaded to unstable (or will soon be: pyosmium & osmcoastline).
> This leaves only two packages in need of a binNMU for the geos transition:
> basemap (1.0.7+dfsg-3)
> player (3.0.2+dfsg-4.2)
> Kind Regards,
> GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1