Bug#1120361: marked as done (transition: gdal)
Your message dated Sat, 15 Nov 2025 06:40:13 +0100
with message-id <6ae6d55c-fd75-4f20-ab3d-5ec1c5c5ea05@debian.org>
and subject line Re: Bug#1120361: transition: gdal
has caused the Debian Bug report #1120361,
regarding transition: gdal
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1120361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120361
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: gdal@packages.debian.org
Control: affects -1 + src:gdal
User: release.debian.org@packages.debian.org
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html
GDAL 3.12.0 bumps its SONAME requiring a transition.
Most rdeps built successfully as summarized below, several were fixed between beta1 & rc1.
ncl (6.6.2.dfsg.1-11) FTBFS due to GCC 15 (#1097439).
paraview (5.13.2+dfsg-3) FTBFS due to VTK 9 (#1114253).
sumo (1.24.0+dfsg1-1) FTBFS due to `const OGRSpatialReference` (#1118731), patch in BTS.
Bugreports:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-gis@lists.debian.org&tag=gdal-3.12
Transition: gdal
libgdal37 (3.11.4+dfsg-1+b1) -> libgdal38 (3.12.0+dfsg-1~exp1)
The status of the most recent rebuilds is as follows.
cloudcompare (2.13.2+git20240821+ds-1) OK
fiona (1.10.1-3) OK
gmt (6.6.0+dfsg-1) OK
grass (8.4.1-1) OK
jeolib-miallib (1.1.7-2) OK
libgeo-gdal-ffi-perl (0.12-1) OK
libosmium (2.22.0-2) OK
mapcache (1.14.1-3) OK
mapnik (4.1.4+ds-1) OK
mapproxy (6.0.1+dfsg-1) OK
mapserver (8.4.1-2) OK
merkaartor (0.20.0+ds-3) OK
ncl (6.6.2.dfsg.1-11) FTBFS (#1097439)
octave-mapping (1.4.3-2) OK
openorienteering-mapper (0.9.5-3.1) OK
openscenegraph (3.6.5+dfsg1-11) OK
paraview (5.13.2+dfsg-3) FTBFS (#1114253)
pgsql-ogr-fdw (1.1.7-2) OK
pktools (2.6.7.6+ds-8) OK
postgis (3.6.0+dfsg-3) OK
pyogrio (0.11.1+ds-1) OK
python-django (3:4.2.26-1) OK
qmapshack (1.18.2-1) OK
r-cran-sf (1.0-19+dfsg-2) OK
r-cran-terra (1.8-70-1) OK
rasterio (1.4.3-4) OK
saga (9.9.3+dfsg-1) OK
survex (1.4.18-1) OK
vtk9 (9.5.2+dfsg2-4) OK
jeolib-jiplib (1.1.6+ds-2) OK
libgdal-grass (1:1.0.4-2) OK
opencv (4.10.0+dfsg-6) OK
osmcoastline (2.4.1-1) OK
qgis (3.40.12+dfsg-1) OK
sumo (1.24.0+dfsg1-1) FTBFS (#1118731) [+]
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
The new gdal migrated to testing and the old was removed which also allowed the removal of the old armadillo.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
Reply to: