[postgis-devel] PSC Vote: PostGIS 2.2.1 release in 2 weeks

[Sebastiaan Couwenberg]

On 20-12-15 14:22, Greg Troxel wrote:
> Sebastiaan Couwenberg <sebastic at xs4all.nl> writes:
>> I'll wait with the backport update for 2.2.1 to transition to testing to
>> not burden its users with two ABI breaks in a short time frame.
> 
> I was considering doing that, but committed my update to 2.2.0.   I
> certainly share your aversion to ABI breaks, but I am curious how many
> packages depend on postgis, and what a user would have to do to deal
> with it.  As a leaf pkgsrc in pkgsrc, I can't quite see it.

SpatiaLite is a reverse dependency of liblwgeom since 4.3.0. That's the
only strict library dependency in Debian.

pgRouting is a reverse dependency of the postgis-2.2 library. This is
not affected by the ABI break. As least where SONAMEs are concerned.


While SpatiaLite is a small package, it's a dependency of GDAL and
through that a dependency of most other GIS packages. A broken
SpatiaLite breaks this entire dependency chain as we experienced with
breakage caused by the removal of lw_vasprintf() from liblwgeom 2.2.0
while Spatialite 4.3.0a still requires it:

 https://groups.google.com/d/topic/spatialite-users/LuFirW-60q4/discussion

Because this broke the QGIS nightly builds, the problem was quickly
found and fixed by backporting the relevant changes from SpatiaLite
4.4.0-RC0. This did not prevent new bugreports in the mean time, all
related to the spatialite link failure, filed for the various packages
depending on GDAL.

I look forward to switching SpatiaLite to the rt-topology library to
have it not require liblwgeom any more. This also breaks the
spatialite->postgis->gdal->spatialite circular dependency that
complicates GEOS transitions as they all depend on it.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1