Your message dated Mon, 8 Sep 2025 07:21:13 +0200
with message-id <[email protected]>
and subject line Re: [DKIM] Bug#1110866: transition: gdal
has caused the Debian Bug report #1110866,
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 [email protected]
immediately.)


-- 
1110866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110866
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:gdal
User: [email protected]
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html

GDAL bumped its SONAME requiring a transition, all rdeps except python-django 
rebuilt successfully as summarized below.


postgis (3.5.2+dfsg-1) FTBFS due to test failures, this is actually caused by 
SFCGAL 2.2.0, and fixed in postgis (3.5.3+dfsg-1).

python-django (3:4.2.23-1) FTBFS due to unrelated reasons.


Transition: gdal

 libgdal36 (3.10.3+dfsg-1) -> libgdal37 (3.11.3+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.6-2)                 OK
 libcitygml              (2.5.2-1)                 OK
 libgeo-gdal-ffi-perl    (0.12-1)                  OK
 libosmium               (2.22.0-1)                OK
 mapcache                (1.14.1-3)                OK
 mapnik                  (4.0.7+ds-1)              OK
 mapproxy                (5.0.0+dfsg-1)            OK
 mapserver               (8.4.0-4)                 OK
 merkaartor              (0.20.0+ds-1)             OK
 mysql-workbench         (8.0.41+dfsg-1)           OK
 ncl                     (6.6.2.dfsg.1-10)         OK
 octave-mapping          (1.4.3-1)                 OK
 openorienteering-mapper (0.9.5-3.1)               OK
 openscenegraph          (3.6.5+dfsg1-9)           OK
 paraview                (5.13.2+dfsg-3)           OK
 pgsql-ogr-fdw           (1.1.7-1)                 OK
 pktools                 (2.6.7.6+ds-6)            OK
 postgis                 (3.5.3+dfsg-1)            OK
 pyogrio                 (0.11.1+ds-1)             OK
 python-django           (3:4.2.23-1)              FTBFS 
 qmapshack               (1.18.0-1)                OK
 r-cran-sf               (1.0-19+dfsg-2)           OK
 r-cran-terra            (1.8-29-1)                OK
 rasterio                (1.4.3-3)                 OK
 saga                    (9.9.1+dfsg-1)            OK
 survex                  (1.4.17-1)                OK
 vtk9                    (9.3.0+dfsg1-4)           OK

 jeolib-jiplib           (1.1.5+ds-1)              OK
 libgdal-grass           (1:1.0.4-1)               OK
 opencv                  (4.10.0+dfsg-5)           OK
 osmcoastline            (2.4.1-1)                 OK
 qgis                    (3.40.9+dfsg-1)           OK
 sumo                    (1.18.0+dfsg-4)           OK


Kind Regards,

Bas

--- End Message ---
--- Begin Message ---
On 8/30/25 7:30 AM, Sebastiaan Couwenberg wrote:
gdal migrated after the libgdal-grass autopkgtest situation on riscv64 got 
resolved.

With the migration on ncl today I had expected the removal of libgdal36 from 
testing, but paraview is keeping it there.

Only the 5.13.2+dfsg-3+b3 binNMU for i386 migrated to testing, the 
amd64/arm64/riscv64/s390x packages are stuck in unstable due to openmpi 
dependencies.

The old gdal packages got removed from testing after the migration of the 
paraview 5.13.2+dfsg-3+b4 packages.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

--- End Message ---

Reply via email to