On 17-08-15 21:50, Sebastiaan Couwenberg wrote: > On 17-08-15 17:32, Sebastiaan Couwenberg wrote: >> 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. > > I've completed the rebuilds of first dependency level, we need to > untangle the spatialite->postgis->gdal->spatialite circular dependency > to make the build dependencies for all these packages installable with > the new libgeos-c1v5 package.
gdal (1.10.1+dfsg-9) FTBFS with spatialite (4.3.0-2) because the libkml GCC 5 transition (#791132) hasn't started yet. This is likely to happen soon, and gdal builds fine after libkml is updated. The procedure to untangle the spatialite->postgis->gdal->spatialite circular dependency also worked as expected, but it's highly inconvenient. We'll likely need to redo it a couple of times for other transitions. We may need to drop the liblwgeom features from spatialite until its split off from postgis in 2.2 or later. > python-shapely (1.4.3-1) needs a patch to not depend on libgeos-c1 > which has been renamed to libgeos-c1v5 for the GCC 5 transition. The > patch has been forwarded in #795883. The issue was already reported > in #795259 so my duplicate bug has been merged. python-shapely (1.5.9-1) was uploaded to unstable to unblock the geos transition. Johan had contributed changes for the 1.5.9 upstream release but that hadn't made it into an upload yet. The package is currently not maintained within the Debian GIS team, I've asked the maintainer to consider moving the package to the team. ossim (1.8.16-4) FTBFS because it expects libgeos_c.so in /usr/lib, but is has moved to the Multi-Arch path for GEOS 3.5.0. I've updated the package to support the Multi-Arch paths, but it requires geos to be updated in unstable first. ossim (1.8.16-5) builds successfully with geos (3.5.0-1). player (3.0.2+dfsg-4.2) still FTBFS, it has already been removed from testing so it's not a blocker. grass (6.4.4-1 / 7.0.1-1~exp1) FTBFS because the wx3.0 transition hasn't completed yet: libwxbase3.0-0v5: Breaks: libwxbase3.0-0 but 3.0.2+dfsg-1 is to be installed. libwxgtk3.0-0v5 : Breaks: libwxgtk3.0-0 but 3.0.2+dfsg-1 is to be installed. libosmium (2.2.0-1) FTBFS because protobuf hasn't been rebuilt for GCC 5 yet. The build fails with many undefined references to `google::protobuf::*' osgearth (2.5.0+dfsg-4 / 2.7.0+dfsg-1~exp2) FTBFS because openscenegraph hasn't been rebuilt for GCC 5 yet. The build fails with many undefined references to `osg*'. osmium (0.0~20150428-7f23002-1) FTBFS like libosmium because protobuf hasn't been rebuilt for GCC 5 yet. osmcoastline (2.0.1-2) FTBFS because of the protobuf issue too. The new (2.1.0-1) version builds fine with the new libosmium (2.3.0-1). qgis (2.8.2+dfsg-3 / 2.8.3+dfsg-1~exp1) FTBFS because grass & osgeath still pull in the old libgeos-c1, we need to get those to build first. Using GEOS 3.5.0 for the GCC 5 transition doesn't seem to be an issue, but there are some other blockers for the transition still. Transition: geos libgeos-3.4.2 (3.4.2-7) -> libgeos-3.5.0 (3.5.0-1) libgeos-c1 (3.4.2-7) -> libgeos-c1v5 (3.5.0-1) The status of the most recent rebuilds is as follows. basemap (1.0.7+dfsg-3) OK osm2pgsql (0.88.0-1 / 0.88.1-1) OK / OK python-shapely (1.5.9-1) OK spatialite (4.3.0-1 / 4.3.0-2 / 4.3.0-3) FTBFS / OK / OK gdal (1.10.1+dfsg-9 / 1.11.2+dfsg-1~exp4) OK / OK / OK / OK postgis (2.1.8+dfsg-1) OK / OK ossim (1.8.16-4 / 1.8.16-5) FTBFS / OK player (3.0.2+dfsg-4.2) FTBFS grass (6.4.4-1 / 7.0.1-1~exp1) FTBFS / FTBFS libosmium (2.2.0-1 / 2.3.0-1) FTBFS / OK mapcache (1.4.0-1) OK mapserver (7.0.0-1) OK osgearth (2.5.0+dfsg-4 / 2.7.0+dfsg-1~exp2) FTBFS / FTBFS osmium (0.0~20150428-7f23002-1) FTBFS pyspatialite (3.0.1-9) OK spatialite-gui (2.0.0~devel2-1) OK spatialite-tools (4.3.0-1) OK osmcoastline (2.0.1-2 / 2.1.0-1) FTBFS / OK pyosmium (2.2.0-1 / 2.3.0-1) OK / OK qgis (2.8.2+dfsg-3 / 2.8.3+dfsg-1~exp1) FTBFS / FTBFS Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
