Bug#992563: marked as done (transition: gdal)
Your message dated Wed, 29 Sep 2021 05:25:18 +0200
with message-id <30233b7d-4bc9-7e8a-8aec-407dd2092938@xs4all.nl>
and subject line Re: Bug#992563: transition: gdal
has caused the Debian Bug report #992563,
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.)
--
992563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992563
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: gdal
- From: Bas Couwenberg <sebastic@xs4all.nl>
- Date: Fri, 20 Aug 2021 11:32:16 +0200
- Message-id: <162945193633.857159.9232265784297099159.reportbug@osiris.linuxminded.xs4all.nl>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: pkg-grass-devel@lists.alioth.debian.org
Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html
Control: block -1 by 992527 992528
For the Debian GIS team I'd like to transition to GDAL 3.3.1.
Most reverse dependencies rebuilt successfully with GDAL 3.3.1 from
experimental as summarized below.
libgdal-grass doesn't need a binNMU as the 3.3.1 version will be
uploaded to unstable instead.
Transition: gdal
libgdal28 (3.2.2+dfsg-2) -> libgdal29 (3.3.1+dfsg-1~exp1)
The status of the most recent rebuilds is as follows.
fiona (1.8.20-2) OK
gazebo (11.1.0+dfsg-6) OK
gmt (6.2.0+dfsg-1) OK
libcitygml (2.0.9-3) OK
libosmium (2.17.0-1) OK
mapcache (1.10.0-2) OK
mapnik (3.1.0+ds-1) OK
mapproxy (1.13.2-1) OK
mapserver (7.6.4-1) OK
merkaartor (0.19.0~rc1+ds-1) OK
mysql-workbench (8.0.26+dfsg-1) OK
ncl (6.6.2-7) OK
node-srs (1.2.0+~2.6.2-1) FTBFS (#992527)
octave-mapping (1.4.1-1) FTBFS (#992528)
openorienteering-mapper (0.9.4-2) OK
openscenegraph (3.6.5+dfsg1-7) OK
pdal (2.2.0+ds-1) OK
pgsql-ogr-fdw (1.1.1-1) OK
pktools (2.6.7.6+ds-3) OK
postgis (3.1.3+dfsg-1) OK
python-django (2:2.2.24-1) OK
qmapshack (1.16.0-1) OK
r-cran-rgdal (1.5-21+dfsg-1) OK
r-cran-sf (0.9-7+dfsg-5) OK
rasterio (1.2.6-1) OK
saga (7.3.0+dfsg-5) OK
vtk6 (6.3.0+dfsg2-8.1) OK
vtk7 (7.1.1+dfsg2-10) OK
vtk9 (9.0.1+dfsg1-8) OK
cloudcompare (2.10.3-4) OK
grass (7.8.5-2) OK
opencv (4.5.1+dfsg-5) OK
osmcoastline (2.3.0-2) OK
paraview (5.9.0-2) OK
sumo (1.8.0+dfsg2-5) OK
libgdal-grass (3.2.2-1 / 3.3.1-1~exp1) FTBFS / OK
otb (7.2.0+dfsg-1) OK
qgis (3.16.10+dfsg-1) OK
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
On 9/27/21 5:42 AM, Sebastiaan Couwenberg wrote:
> That just leaves opencv on mipsel which update_excuses suggests is
> blocked by vtk9, and qgis on mips* which is waiting for FTP master to
> act on #994053.
opencv on mipsel has migrated, and qgis on mips* has been removed.
RM bugreports also exist for node-srs and its rdeps which will fix the
remaining issue in unstable too.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
Reply to: