Bug#973600: transition: gdal
On 2020-12-07 12:30:10 +0100, Sebastiaan Couwenberg wrote: > On 12/6/20 12:37 PM, Sebastian Ramacher wrote: > > On 2020-11-02 12:49:04 +0100, Bas Couwenberg wrote: > >> Package: release.debian.org > >> Severity: normal > >> User: release.debian@packages.debian.org > >> Usertags: transition > >> X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org > >> Control: forwarded -1 > >> https://release.debian.org/transitions/html/auto-gdal.html > >> > >> For the Debian GIS team I'd like to transition to GDAL 3.2.0. > >> > >> All reverse dependencies rebuilt successfully with GDAL 3.2.0 from > >> experimental as summarized below, except mysql-workbench. > >> > >> libgdal-grass doesn't need a binNMU as the 3.2.0 version will be > >> uploaded to unstable instead. > > > > Please go ahead with the uploads to unstable. > > Thanks for quickly scheduling the binNMU even before it was installed on > all release architectures. > > Please also binNMU grass & postgis in experimental. Scheduled. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#973600: transition: gdal
On Tue, 8 Dec 2020 at 09:49, Graham Inggs wrote: > I'll test and upload if successful. Ah, built successfully on arm64, failed on armhf. :( What Adrian wrote in #976802 sounds promising: "Since the new r-cran-sf build dependency seems to be only required for tests, removing it (also from the autopkgtest?) might be the easiest short-term solution." I'm going to try that now.
Bug#973600: transition: gdal
On Tue, 8 Dec 2020 at 07:48, Sebastiaan Couwenberg wrote: > What should we do about r-cran-sf which cannot be built on most release > archs due to r-cran-s2 failing to build there (#976473). > > Should be file an RM bugreport to have r-cran-sf (and possible rdeps) > removed from those release architectures, or should it be hinted out of > testing? Well, first prize would be to fix r-cran-s2. Luckily, it seems to be already done upstream for arm64 [1], thanks to everyone's excitement about the Apple M1 silicon. I'll test and upload if successful. [1] https://github.com/r-spatial/s2/commit/76db560b9fe1b4dc4edbb6578fd1c132f130e820
Bug#973600: transition: gdal
On 12/7/20 12:30 PM, Sebastiaan Couwenberg wrote: > On 12/6/20 12:37 PM, Sebastian Ramacher wrote: >> On 2020-11-02 12:49:04 +0100, Bas Couwenberg wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian@packages.debian.org >>> Usertags: transition >>> X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org >>> Control: forwarded -1 >>> https://release.debian.org/transitions/html/auto-gdal.html >>> >>> For the Debian GIS team I'd like to transition to GDAL 3.2.0. >>> >>> All reverse dependencies rebuilt successfully with GDAL 3.2.0 from >>> experimental as summarized below, except mysql-workbench. >>> >>> libgdal-grass doesn't need a binNMU as the 3.2.0 version will be >>> uploaded to unstable instead. >> >> Please go ahead with the uploads to unstable. > > Thanks for quickly scheduling the binNMU even before it was installed on > all release architectures. > > Please also binNMU grass & postgis in experimental. What should we do about r-cran-sf which cannot be built on most release archs due to r-cran-s2 failing to build there (#976473). Should be file an RM bugreport to have r-cran-sf (and possible rdeps) removed from those release architectures, or should it be hinted out of testing? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#973600: transition: gdal
On 12/6/20 12:37 PM, Sebastian Ramacher wrote: > On 2020-11-02 12:49:04 +0100, Bas Couwenberg wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org >> Control: forwarded -1 >> https://release.debian.org/transitions/html/auto-gdal.html >> >> For the Debian GIS team I'd like to transition to GDAL 3.2.0. >> >> All reverse dependencies rebuilt successfully with GDAL 3.2.0 from >> experimental as summarized below, except mysql-workbench. >> >> libgdal-grass doesn't need a binNMU as the 3.2.0 version will be >> uploaded to unstable instead. > > Please go ahead with the uploads to unstable. Thanks for quickly scheduling the binNMU even before it was installed on all release architectures. Please also binNMU grass & postgis in experimental. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#973600: transition: gdal
Control: tags -1 + confirmed On 2020-11-02 12:49:04 +0100, Bas Couwenberg wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-gdal.html > > For the Debian GIS team I'd like to transition to GDAL 3.2.0. > > All reverse dependencies rebuilt successfully with GDAL 3.2.0 from > experimental as summarized below, except mysql-workbench. > > libgdal-grass doesn't need a binNMU as the 3.2.0 version will be > uploaded to unstable instead. Please go ahead with the uploads to unstable. Cheers > > > Transition: gdal > > libgdal27 (3.1.4+dfsg-1) -> libgdal28 (3.2.0~rc1+dfsg-1~exp1) > > The status of the most recent rebuilds is as follows. > > fiona (1.8.17-1)OK > gazebo (11.1.0+dfsg-3) OK > gmt (6.1.1+dfsg-1)OK > libcitygml (2.0.9-2) OK > libosmium (2.15.6-1)OK > mapcache(1.10.0-1)OK > mapnik (3.0.23+ds-1) OK > mapproxy(1.12.0-2)OK > mapserver (7.6.1-1) OK > merkaartor (0.18.4+ds-4) OK > mysql-workbench (8.0.19+dfsg-1) FTBFS >(#937102) > ncl (6.6.2-6) OK > node-srs(1.2.0+~2.2.0~git20200927.f30387d8-2) OK > octave-mapping (1.4.1-1) OK > openorienteering-mapper (0.9.4-1) OK > openscenegraph (3.6.5+dfsg1-6) OK > pdal(2.2.0+ds-1) OK > pgsql-ogr-fdw (1.0.12-2)OK > pktools (2.6.7.6+ds-2)OK > postgis (3.0.2+dfsg-4)OK > python-django (2:2.2.16-1) OK > qmapshack (1.15.0-1)OK > r-cran-rgdal(1.5-18+dfsg-1) OK > r-cran-sf (0.9-5+dfsg-1)OK > rasterio(1.1.8-1) OK > saga(7.3.0+dfsg-4)OK > sumo(1.4.0+dfsg1-1) OK > vtk6(6.3.0+dfsg2-5) OK > vtk7(7.1.1+dfsg2-4) OK > > cloudcompare(2.10.3-4)OK > grass (7.8.4-2) OK > opencv (4.2.0+dfsg-6)OK > osmcoastline(2.2.4-1) OK > paraview(5.7.0-5) OK > pyosmium(3.0.1-2) OK > > libgdal-grass (3.1.4-1 / 3.2.0~rc1-1~exp1) FTBFS/OK > otb (7.2.0+dfsg-1)OK > qgis(3.10.11+dfsg-1) OK > > > Kind Regards, > > Bas > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#973600: transition: gdal
On 11/2/20 12:49 PM, Bas Couwenberg wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-gdal.html > > For the Debian GIS team I'd like to transition to GDAL 3.2.0. > > All reverse dependencies rebuilt successfully with GDAL 3.2.0 from > experimental as summarized below, except mysql-workbench. > > libgdal-grass doesn't need a binNMU as the 3.2.0 version will be > uploaded to unstable instead. Can we do this after the python3-defaults transition (#972253)? I really want to get this done before the transition freeze. > Transition: gdal > > libgdal27 (3.1.4+dfsg-1) -> libgdal28 (3.2.0~rc1+dfsg-1~exp1) > > The status of the most recent rebuilds is as follows. > > fiona (1.8.17-1)OK > gazebo (11.1.0+dfsg-3) OK > gmt (6.1.1+dfsg-1)OK > libcitygml (2.0.9-2) OK > libosmium (2.15.6-1)OK > mapcache(1.10.0-1)OK > mapnik (3.0.23+ds-1) OK > mapproxy(1.12.0-2)OK > mapserver (7.6.1-1) OK > merkaartor (0.18.4+ds-4) OK > mysql-workbench (8.0.19+dfsg-1) FTBFS >(#937102) > ncl (6.6.2-6) OK > node-srs(1.2.0+~2.2.0~git20200927.f30387d8-2) OK > octave-mapping (1.4.1-1) OK > openorienteering-mapper (0.9.4-1) OK > openscenegraph (3.6.5+dfsg1-6) OK > pdal(2.2.0+ds-1) OK > pgsql-ogr-fdw (1.0.12-2)OK > pktools (2.6.7.6+ds-2)OK > postgis (3.0.2+dfsg-4)OK > python-django (2:2.2.16-1) OK > qmapshack (1.15.0-1)OK > r-cran-rgdal(1.5-18+dfsg-1) OK > r-cran-sf (0.9-5+dfsg-1)OK > rasterio(1.1.8-1) OK > saga(7.3.0+dfsg-4)OK > sumo(1.4.0+dfsg1-1) OK > vtk6(6.3.0+dfsg2-5) OK > vtk7(7.1.1+dfsg2-4) OK > > cloudcompare(2.10.3-4)OK > grass (7.8.4-2) OK > opencv (4.2.0+dfsg-6)OK > osmcoastline(2.2.4-1) OK > paraview(5.7.0-5) OK > pyosmium(3.0.1-2) OK > > libgdal-grass (3.1.4-1 / 3.2.0~rc1-1~exp1) FTBFS/OK > otb (7.2.0+dfsg-1)OK > qgis(3.10.11+dfsg-1) OK Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#973600: transition: gdal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html For the Debian GIS team I'd like to transition to GDAL 3.2.0. All reverse dependencies rebuilt successfully with GDAL 3.2.0 from experimental as summarized below, except mysql-workbench. libgdal-grass doesn't need a binNMU as the 3.2.0 version will be uploaded to unstable instead. Transition: gdal libgdal27 (3.1.4+dfsg-1) -> libgdal28 (3.2.0~rc1+dfsg-1~exp1) The status of the most recent rebuilds is as follows. fiona (1.8.17-1)OK gazebo (11.1.0+dfsg-3) OK gmt (6.1.1+dfsg-1)OK libcitygml (2.0.9-2) OK libosmium (2.15.6-1)OK mapcache(1.10.0-1)OK mapnik (3.0.23+ds-1) OK mapproxy(1.12.0-2)OK mapserver (7.6.1-1) OK merkaartor (0.18.4+ds-4) OK mysql-workbench (8.0.19+dfsg-1) FTBFS (#937102) ncl (6.6.2-6) OK node-srs(1.2.0+~2.2.0~git20200927.f30387d8-2) OK octave-mapping (1.4.1-1) OK openorienteering-mapper (0.9.4-1) OK openscenegraph (3.6.5+dfsg1-6) OK pdal(2.2.0+ds-1) OK pgsql-ogr-fdw (1.0.12-2)OK pktools (2.6.7.6+ds-2)OK postgis (3.0.2+dfsg-4)OK python-django (2:2.2.16-1) OK qmapshack (1.15.0-1)OK r-cran-rgdal(1.5-18+dfsg-1) OK r-cran-sf (0.9-5+dfsg-1)OK rasterio(1.1.8-1) OK saga(7.3.0+dfsg-4)OK sumo(1.4.0+dfsg1-1) OK vtk6(6.3.0+dfsg2-5) OK vtk7(7.1.1+dfsg2-4) OK cloudcompare(2.10.3-4)OK grass (7.8.4-2) OK opencv (4.2.0+dfsg-6)OK osmcoastline(2.2.4-1) OK paraview(5.7.0-5) OK pyosmium(3.0.1-2) OK libgdal-grass (3.1.4-1 / 3.2.0~rc1-1~exp1) FTBFS/OK otb (7.2.0+dfsg-1)OK qgis(3.10.11+dfsg-1) OK Kind Regards, Bas
