GDAL 3.8.0
The first release candidate for GDAL 3.8.0 has been released.
Most of the build failures have the same cause:
In file included from /usr/include/gdal/ogr_geometry.h:36,
from
/build/osmcoastline-2.4.0/src/coastline_polygons.hpp:25,
from
/build/osmcoastline-2.4.0/src/coastline_ring_collection.cpp:22:
/usr/include/gdal/cpl_json.h:97:36: error: expected ')' before 'nVal'
97 | explicit CPLJSONObject(uint64_t nVal);
| ~ ^~~~~
| )
/usr/include/gdal/cpl_json.h:119:41: error: 'uint64_t' has not been
declared
119 | void Add(const std::string &osName, uint64_t nValue);
| ^~~~~~~~
/usr/include/gdal/cpl_json.h:119:10: error: 'void
CPLJSONObject::Add(const std::string&, int)' cannot be overloaded with
'void CPLJSONObject::Add(const std::string&, int)'
119 | void Add(const std::string &osName, uint64_t nValue);
| ^~~
/usr/include/gdal/cpl_json.h:117:10: note: previous declaration 'void
CPLJSONObject::Add(const std::string&, int)'
117 | void Add(const std::string &osName, int nValue);
| ^~~
/usr/include/gdal/cpl_json.h:131:41: error: 'uint64_t' has not been
declared
131 | void Set(const std::string &osName, uint64_t nValue);
| ^~~~~~~~
/usr/include/gdal/cpl_json.h:131:10: error: 'void
CPLJSONObject::Set(const std::string&, int)' cannot be overloaded with
'void CPLJSONObject::Set(const std::string&, int)'
131 | void Set(const std::string &osName, uint64_t nValue);
| ^~~
/usr/include/gdal/cpl_json.h:129:10: note: previous declaration 'void
CPLJSONObject::Set(const std::string&, int)'
129 | void Set(const std::string &osName, int nValue);
| ^~~
/usr/include/gdal/cpl_json.h:245:14: error: 'uint64_t' has not been
declared
245 | void Add(uint64_t nValue);
| ^~~~~~~~
/usr/include/gdal/cpl_json.h:245:10: error: 'void
CPLJSONArray::Add(int)' cannot be overloaded with 'void
CPLJSONArray::Add(int)'
245 | void Add(uint64_t nValue);
| ^~~
/usr/include/gdal/cpl_json.h:243:10: note: previous declaration 'void
CPLJSONArray::Add(int)'
243 | void Add(int nValue);
| ^~~
Fixing this will resolves most blockers.
libgeo-gdal-ffi-perl (0.1-2) FTBFS due to test failures. (#1055581)
mysql-workbench (8.0.32+dfsg-1) FTBFS due to unrelated issues. (#1051433)
pktools (2.6.7.6+ds-4) FTBFS due to type errors. (#1055587)
r-cran-rgdal (1.6-7+dfsg-1) FTBFS due to type errors. (#1055589)
r-cran-sf (1.0-14+dfsg-1) FTBFS due to type errors. (#1055590)
rasterio (1.3.9-1) FTBFS due to test failures. (#1055594)
facet-analyser (0.0~git20221121142040.6be10b8+ds1-3) cannot be built due
to #1040334.
libgdal-grass (1:1.0.2-6) FTBFS due to type errors. (#1055602)
osmcoastline (2.4.0-2) FTBFS due to type errors. (#1055604)
Bugreports:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-gis@lists.debian.org&tag=gdal-3.8
Transition: gdal
libgdal33 (3.7.3+dfsg-1) -> libgdal34 (3.8.0~rc1+dfsg-1~exp1)
The status of the most recent rebuilds is as follows.
cloudcompare (2.11.3-7.1) OK
fiona (1.9.5-1) OK
gmt (6.4.0+dfsg-2) OK
grass (8.3.1-1) OK
libcitygml (2.5.1-1) OK
libgeo-gdal-ffi-perl (0.1-2) FTBFS
(#1055581)
libosmium (2.20.0-1) OK
mapcache (1.14.0-2) OK
mapnik (3.1.0+ds-4) OK
mapproxy (1.16.0+dfsg-1) OK
mapserver (8.0.1-2) OK
merkaartor (0.19.0+ds-4) OK
mysql-workbench (8.0.32+dfsg-1) FTBFS
(#1051433)
ncl (6.6.2.dfsg.1-2) OK
octave-mapping (1.4.2-3) OK
openorienteering-mapper (0.9.5-3.1) OK
openscenegraph (3.6.5+dfsg1-8) OK
paraview (5.11.0+dfsg-2) OK
pgsql-ogr-fdw (1.1.4-3) OK
pktools (2.6.7.6+ds-4) FTBFS
(#1055587)
postgis (3.4.0+dfsg-3) OK
python-django (3:4.2.6-1) OK
qmapshack (1.17.0-1) OK
r-cran-rgdal (1.6-7+dfsg-1) FTBFS
(#1055589)
r-cran-sf (1.0-14+dfsg-1) FTBFS
(#1055590)
r-cran-terra (1.7-55-1) OK
rasterio (1.3.9-1) FTBFS
(#1055594)
saga (9.2.0+dfsg-1) OK
vtk9 (9.1.0+really9.1.0+dfsg2-7) OK
facet-analyser (0.0~git20221121142040.6be10b8+ds1-3) BD-UNINST
libgdal-grass (1:1.0.2-6) FTBFS
(#1055602)
opencv (4.6.0+dfsg-13) OK
osmcoastline (2.4.0-2) FTBFS
(#1055604)
qgis (3.28.12+dfsg-1) OK
sumo (1.18.0+dfsg-3) OK
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: