GEOS 3.5.0
GEOS 3.5.0 was released yesterday, I've just updated the packaging in
the experimental branch but have not uploaded the package yet.
The GCC 5 related geos transition hasn't started yet, but experimental
already has the updated geos package for it.
The API changes don't look very worrying, but I'd like to verify that
all reverse dependencies still build with GEOS 3.5.0 before uploading it
to experimental. I don't want to holdup the GCC 5 transitions in case of
breakage.
GEOS 3.5.0 will be required for many of the new features in the upcoming
PostGIS 2.2 release, refer to the 'PSC vote Request: Make Geos 3.5 the
default in PostGIS 2.2' thread [1] on the postgis-devel list for
backgrounds.
With the PostGIS considerations in mind, I'd like to use GEOS 3.5.0 in
the GCC 5 related geos transition [2] if the reverse dependencies build
successfully.
[1] https://lists.osgeo.org/pipermail/postgis-devel/2015-May/024878.html
[2] https://bugs.debian.org/791045
Transition: geos
libgeos-3.4.2v5 (3.4.2-8~exp3) -> libgeos-3.5.0 (3.5.0-1)
libgeos-c1v5 (3.4.2-8~exp3) -> libgeos-c1v5 (3.5.0-1)
The status of the most recent rebuilds is as follows.
basemap (1.0.7+dfsg-3) TODO
gdal (1.10.1+dfsg-9 / 1.11.2+dfsg-1~exp4) TODO / TODO
osm2pgsql (0.88.0-1 / 0.88.1-1) TODO / TODO
ossim (1.8.16-4) TODO
player (3.0.2+dfsg-4.2) TODO
postgis (2.1.8+dfsg-1) TODO
python-shapely (1.4.3-1) TODO
spatialite (4.3.0-1) TODO
grass (6.4.4-1 / 7.0.1-1~exp1) TODO / TODO
libosmium (2.2.0-1) TODO
mapcache (1.4.0-1) TODO
mapserver (7.0.0-1) TODO
osgearth (2.5.0+dfsg-4 / 2.7.0+dfsg-1~exp2) TODO / TODO
osmium (0.0~20150428-7f23002-1) TODO
pyspatialite (3.0.1-9) TODO
spatialite-gui (2.0.0~devel2-1) TODO
spatialite-tools (4.3.0-1) TODO
osmcoastline (2.0.1-2) TODO
pyosmium (2.2.0-1) TODO
qgis (2.8.2+dfsg-3 / 2.8.3+dfsg-1~exp1) TODO / TODO
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: