On 10/26/2016 06:36 PM, Sebastiaan Couwenberg wrote: > GEOS 3.5.1 & 3.6.0 have been released, since the changes in 3.6.0 don't > look very worrying upgrading to 3.6.0 for stretch seems like the best > option (since a transition will be required for either). > > [...] > > Since only the reverse dependencies C++ library need to be rebuilt, the > transition will be limited. But based on the rebuilds so far, we may be > better off transitioning to 3.5.1 instead, since the projects that rely > on the C++ API pretty much all FTBFS with GEOS 3.6.0.
The rebuilds with GEOS 3.5.1 look much better as expected, all C++ reverse dependencies do build successfully with GEOS 3.5.1. I've asked the FTP masters to reject GEOS 3.6.0 in NEW, and uploaded GEOS 3.5.1 instead. Transition: geos libgeos-c1v5 (3.5.0-4) -> libgeos-c1v5 (3.5.1-1~exp1) libgeos-3.5.0 (3.5.0-4) -> libgeos-3.6.0 (3.5.1-1~exp1) The status of the most recent rebuilds is as follows. basemap (1.0.7+dfsg-4) SKIP (no C++) / OK librttopo (1.0.0-1) SKIP (no C++) / OK ossim (1.8.20.3+ds-5) OK python-shapely (1.5.17-1) SKIP (no C++) / OK spatialite (4.3.0a-5) SKIP (no C++) / OK gdal (2.1.1+dfsg-5) SKIP (no C++) / OK pyspatialite (3.0.1-11) SKIP (no C++) / OK spatialite-gui (2.0.0~devel2-4) SKIP (no C++) / OK spatialite-tools (4.3.0-2) SKIP (no C++) / OK grass (7.0.5-2) OK imposm (2.6.0+ds-3) SKIP (no C++) / OK libosmium (2.9.0-2) OK mapcache (1.4.1-3) SKIP (no C++) / OK mapserver (7.0.2-1) SKIP (no C++) / OK osgearth (2.7.0+dfsg-2) SKIP (no C++) / OK osmium (0.0~20160425-e2e4368-2) OK pdal (1.3.0-1) SKIP (no C++) / OK postgis (2.3.0+dfsg-3) SKIP (no C++) / OK osm2pgsql (0.90.1+ds-1) OK osmcoastline (2.1.4-1) SKIP (no C++) / OK pyosmium (2.9.0-1) SKIP (no C++) / OK qgis (2.14.7+dfsg-2) SKIP (no C++) / OK Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
