Bug#992563: transition: gdal
On 9/23/21 11:40 AM, Sebastian Ramacher wrote: > On 2021-09-23 11:34:21, Sebastiaan Couwenberg wrote: >> On 9/18/21 9:57 AM, Sebastian Ramacher wrote: >>> On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: Quite a few packages on mipsel may need a binNMU for the recent glibc changes, it allowed libgdal-grass to migrate, but there a still quite a few packages with remaining issues: https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html >>> >>> There are a over 200 packages and a bunch of binNMUs that are blocked by >>> glibc. I'm slowly wading through that list. >> >> glibc migrated to testing, this allowed a few packages that are part of >> the gdal & pdal transitions to migrate but there are still outstanding >> issues. >> >> In the britney update_output.txt you see these packages as reasons why >> the old gdal & pdal library cannot be removed, but you don't see >> attempts to migrate those packages. >> >> r-cran-rgdal and r-cran-sf are blocked by r-base. > > They have been binNMUed in testing-proposed-updates and should migrate > to testing in the next run. > >> >> What is preventing vtk7 and paraview from migrating? > >>From https://release.debian.org/britney/update_excuses.html: both the > paraview and vtk7 binNMUs are blocked by openmpi. postgis, paraview, and vtk7 migrated to testing as well. 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. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 9/23/21 11:47 PM, Sebastian Ramacher wrote: > On 2021-09-23 11:44:14 +0200, Sebastiaan Couwenberg wrote: >> There is also postgis which is blocked by a piuparts regression that's >> not actually caused by postgis. piuparts-de...@alioth-lists.debian.net >> has been contacted about that last week, but no response so far. > > Why is it failing? Have bugs been filed for this issue? Because postgresql-common removed the wrong file, see: https://salsa.debian.org/postgresql/postgresql-common/-/commit/27b62a5edd2e07d6242e51cae2414f4487fbe370 I can't find a bugreport for it. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 2021-09-23 11:44:14 +0200, Sebastiaan Couwenberg wrote: > On 9/23/21 11:40 AM, Sebastian Ramacher wrote: > > On 2021-09-23 11:34:21, Sebastiaan Couwenberg wrote: > >> On 9/18/21 9:57 AM, Sebastian Ramacher wrote: > >>> On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: > On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: > > Quite a few packages on mipsel may need a binNMU for the recent glibc > changes, it allowed libgdal-grass to migrate, but there a still quite a > few packages with remaining issues: > > https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html > >>> > >>> There are a over 200 packages and a bunch of binNMUs that are blocked by > >>> glibc. I'm slowly wading through that list. > >> > >> glibc migrated to testing, this allowed a few packages that are part of > >> the gdal & pdal transitions to migrate but there are still outstanding > >> issues. > >> > >> In the britney update_output.txt you see these packages as reasons why > >> the old gdal & pdal library cannot be removed, but you don't see > >> attempts to migrate those packages. > >> > >> r-cran-rgdal and r-cran-sf are blocked by r-base. > > > > They have been binNMUed in testing-proposed-updates and should migrate > > to testing in the next run. > > > >> What is preventing vtk7 and paraview from migrating? > > > >>From https://release.debian.org/britney/update_excuses.html: both the > > paraview and vtk7 binNMUs are blocked by openmpi. > > Thanks, I was looking at: > > https://qa.debian.org/excuses.php?package=paraview > https://qa.debian.org/excuses.php?package=vtk7 > > There is also postgis which is blocked by a piuparts regression that's > not actually caused by postgis. piuparts-de...@alioth-lists.debian.net > has been contacted about that last week, but no response so far. Why is it failing? Have bugs been filed for this issue? Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#992563: transition: gdal
On 9/23/21 11:40 AM, Sebastian Ramacher wrote: > On 2021-09-23 11:34:21, Sebastiaan Couwenberg wrote: >> On 9/18/21 9:57 AM, Sebastian Ramacher wrote: >>> On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: Quite a few packages on mipsel may need a binNMU for the recent glibc changes, it allowed libgdal-grass to migrate, but there a still quite a few packages with remaining issues: https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html >>> >>> There are a over 200 packages and a bunch of binNMUs that are blocked by >>> glibc. I'm slowly wading through that list. >> >> glibc migrated to testing, this allowed a few packages that are part of >> the gdal & pdal transitions to migrate but there are still outstanding >> issues. >> >> In the britney update_output.txt you see these packages as reasons why >> the old gdal & pdal library cannot be removed, but you don't see >> attempts to migrate those packages. >> >> r-cran-rgdal and r-cran-sf are blocked by r-base. > > They have been binNMUed in testing-proposed-updates and should migrate > to testing in the next run. > >> What is preventing vtk7 and paraview from migrating? > >>From https://release.debian.org/britney/update_excuses.html: both the > paraview and vtk7 binNMUs are blocked by openmpi. Thanks, I was looking at: https://qa.debian.org/excuses.php?package=paraview https://qa.debian.org/excuses.php?package=vtk7 There is also postgis which is blocked by a piuparts regression that's not actually caused by postgis. piuparts-de...@alioth-lists.debian.net has been contacted about that last week, but no response so far. Can that issue be ignored to let it migrate? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 2021-09-23 11:40:15, Sebastian Ramacher wrote: > On 2021-09-23 11:34:21, Sebastiaan Couwenberg wrote: > > On 9/18/21 9:57 AM, Sebastian Ramacher wrote: > > > On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: > > >> On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: > > >> > > >> Quite a few packages on mipsel may need a binNMU for the recent glibc > > >> changes, it allowed libgdal-grass to migrate, but there a still quite a > > >> few packages with remaining issues: > > >> > > >> https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html > > > > > > There are a over 200 packages and a bunch of binNMUs that are blocked by > > > glibc. I'm slowly wading through that list. > > > > glibc migrated to testing, this allowed a few packages that are part of > > the gdal & pdal transitions to migrate but there are still outstanding > > issues. > > > > In the britney update_output.txt you see these packages as reasons why > > the old gdal & pdal library cannot be removed, but you don't see > > attempts to migrate those packages. > > > > r-cran-rgdal and r-cran-sf are blocked by r-base. > > They have been binNMUed in testing-proposed-updates and should migrate > to testing in the next run. > > > > > What is preventing vtk7 and paraview from migrating? > > From https://release.debian.org/britney/update_excuses.html: both the > paraview and vtk7 binNMUs are blocked by openmpi. A fix for gyoto was uploaded, so openmpi should be able to migrate in a few days. Cheers -- Sebastian Ramacher
Bug#992563: transition: gdal
On 2021-09-23 11:34:21, Sebastiaan Couwenberg wrote: > On 9/18/21 9:57 AM, Sebastian Ramacher wrote: > > On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: > >> On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: > >> > >> Quite a few packages on mipsel may need a binNMU for the recent glibc > >> changes, it allowed libgdal-grass to migrate, but there a still quite a > >> few packages with remaining issues: > >> > >> https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html > > > > There are a over 200 packages and a bunch of binNMUs that are blocked by > > glibc. I'm slowly wading through that list. > > glibc migrated to testing, this allowed a few packages that are part of > the gdal & pdal transitions to migrate but there are still outstanding > issues. > > In the britney update_output.txt you see these packages as reasons why > the old gdal & pdal library cannot be removed, but you don't see > attempts to migrate those packages. > > r-cran-rgdal and r-cran-sf are blocked by r-base. They have been binNMUed in testing-proposed-updates and should migrate to testing in the next run. > > What is preventing vtk7 and paraview from migrating? >From https://release.debian.org/britney/update_excuses.html: both the paraview and vtk7 binNMUs are blocked by openmpi. Cheers -- Sebastian Ramacher
Bug#992563: transition: gdal
On 9/18/21 9:57 AM, Sebastian Ramacher wrote: > On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: >> On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: >> >> Quite a few packages on mipsel may need a binNMU for the recent glibc >> changes, it allowed libgdal-grass to migrate, but there a still quite a >> few packages with remaining issues: >> >> https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html > > There are a over 200 packages and a bunch of binNMUs that are blocked by > glibc. I'm slowly wading through that list. glibc migrated to testing, this allowed a few packages that are part of the gdal & pdal transitions to migrate but there are still outstanding issues. In the britney update_output.txt you see these packages as reasons why the old gdal & pdal library cannot be removed, but you don't see attempts to migrate those packages. r-cran-rgdal and r-cran-sf are blocked by r-base. What is preventing vtk7 and paraview from migrating? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 2021-09-18 07:01:38 +0200, Sebastiaan Couwenberg wrote: > On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: > > grass & otb in experiment still need to be rebuilt. > > grass had a source upload, only otb in experimental needs a binNMU now. otb in experimental scheduled. > > Quite a few packages on mipsel may need a binNMU for the recent glibc > changes, it allowed libgdal-grass to migrate, but there a still quite a > few packages with remaining issues: > > https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html There are a over 200 packages and a bunch of binNMUs that are blocked by glibc. I'm slowly wading through that list. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#992563: transition: gdal
On 9/12/21 7:54 PM, Sebastiaan Couwenberg wrote: > grass & otb in experiment still need to be rebuilt. grass had a source upload, only otb in experimental needs a binNMU now. Quite a few packages on mipsel may need a binNMU for the recent glibc changes, it allowed libgdal-grass to migrate, but there a still quite a few packages with remaining issues: https://linuxminded.nl/debian/gis-transitions/testing/html/gdal.html Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 9/11/21 5:56 PM, Sebastian Ramacher wrote: > On 2021-09-11 17:02:48 +0200, Sebastiaan Couwenberg wrote: >> On 9/10/21 9:35 AM, Sebastian Ramacher wrote: >>> On 2021-09-09 13:02:14, Sebastiaan Couwenberg wrote: On 9/9/21 5:57 AM, Sebastiaan Couwenberg wrote: > On 9/8/21 6:56 AM, Sebastiaan Couwenberg wrote: >> On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: >>> On 9/5/21 6:48 PM, Sebastian Ramacher wrote: On 2021-08-20 11:32:16 +0200, 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 > 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. Assuming that the version of pdal in experimental also builds fine against the new version of gdal, please go ahead and also start the pdal transition. >>> >>> PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to >>> unstable once gdal is built on all release architectures. The gdal >>> upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to >>> testing to fix #993334 there too. >> >> gdal has built on all release architectures, and pdal has been uploaded >> to unstable as well. > > Thanks for scheduling the binNMUs, please also binNMU grass to unblock > libgdal-grass & qgis. libgdal-grass needs a source upload as usual. grass has been rebuilt on all release architectures too, qgis can be rebuilt now. >>> >>> The binNMUs for qgis have also been scheduled. >> >> RM bugreports for ncl (i386) and qgis (mipsel mips64el) have been filed. > > The one for ncl won't be needed. It won't block libgdal from migrating > to testing. It will only delay the removal of the old binary packages on > i386 until it's fixed. Everything that keeps libgdal28 around blocks the removal of libepsilon (#994073). > And to be honest, I don't think that a RoQA for a package where the > maintainer is actively working on fixing it is appropriate. That's not what that ncl bugreport shows. >> grass (7.8.6~rc2-1~exp1) and otb (8.0.0~alpha1+dfsg-1~exp1) in >> experimental also need to be rebuilt. grass & otb in experiment still need to be rebuilt. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 2021-09-11 17:02:48 +0200, Sebastiaan Couwenberg wrote: > On 9/10/21 9:35 AM, Sebastian Ramacher wrote: > > On 2021-09-09 13:02:14, Sebastiaan Couwenberg wrote: > >> On 9/9/21 5:57 AM, Sebastiaan Couwenberg wrote: > >>> On 9/8/21 6:56 AM, Sebastiaan Couwenberg wrote: > On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: > > On 9/5/21 6:48 PM, Sebastian Ramacher wrote: > >> On 2021-08-20 11:32:16 +0200, 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 > >>> 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. > >> > >> Assuming that the version of pdal in experimental also builds fine > >> against the new version of gdal, please go ahead and also start the > >> pdal > >> transition. > > > > PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to > > unstable once gdal is built on all release architectures. The gdal > > upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to > > testing to fix #993334 there too. > > gdal has built on all release architectures, and pdal has been uploaded > to unstable as well. > >>> > >>> Thanks for scheduling the binNMUs, please also binNMU grass to unblock > >>> libgdal-grass & qgis. libgdal-grass needs a source upload as usual. > >> > >> grass has been rebuilt on all release architectures too, qgis can be > >> rebuilt now. > > > > The binNMUs for qgis have also been scheduled. > > RM bugreports for ncl (i386) and qgis (mipsel mips64el) have been filed. The one for ncl won't be needed. It won't block libgdal from migrating to testing. It will only delay the removal of the old binary packages on i386 until it's fixed. And to be honest, I don't think that a RoQA for a package where the maintainer is actively working on fixing it is appropriate. Cheers > > grass (7.8.6~rc2-1~exp1) and otb (8.0.0~alpha1+dfsg-1~exp1) in > experimental also need to be rebuilt. > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#992563: transition: gdal
On 9/10/21 9:35 AM, Sebastian Ramacher wrote: > On 2021-09-09 13:02:14, Sebastiaan Couwenberg wrote: >> On 9/9/21 5:57 AM, Sebastiaan Couwenberg wrote: >>> On 9/8/21 6:56 AM, Sebastiaan Couwenberg wrote: On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: > On 9/5/21 6:48 PM, Sebastian Ramacher wrote: >> On 2021-08-20 11:32:16 +0200, 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 >>> 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. >> >> Assuming that the version of pdal in experimental also builds fine >> against the new version of gdal, please go ahead and also start the pdal >> transition. > > PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to > unstable once gdal is built on all release architectures. The gdal > upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to > testing to fix #993334 there too. gdal has built on all release architectures, and pdal has been uploaded to unstable as well. >>> >>> Thanks for scheduling the binNMUs, please also binNMU grass to unblock >>> libgdal-grass & qgis. libgdal-grass needs a source upload as usual. >> >> grass has been rebuilt on all release architectures too, qgis can be >> rebuilt now. > > The binNMUs for qgis have also been scheduled. RM bugreports for ncl (i386) and qgis (mipsel mips64el) have been filed. grass (7.8.6~rc2-1~exp1) and otb (8.0.0~alpha1+dfsg-1~exp1) in experimental also need to be rebuilt. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 2021-09-09 13:02:14, Sebastiaan Couwenberg wrote: > On 9/9/21 5:57 AM, Sebastiaan Couwenberg wrote: > > On 9/8/21 6:56 AM, Sebastiaan Couwenberg wrote: > >> On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: > >>> On 9/5/21 6:48 PM, Sebastian Ramacher wrote: > On 2021-08-20 11:32:16 +0200, 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 > > 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. > > Assuming that the version of pdal in experimental also builds fine > against the new version of gdal, please go ahead and also start the pdal > transition. > >>> > >>> PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to > >>> unstable once gdal is built on all release architectures. The gdal > >>> upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to > >>> testing to fix #993334 there too. > >> > >> gdal has built on all release architectures, and pdal has been uploaded > >> to unstable as well. > > > > Thanks for scheduling the binNMUs, please also binNMU grass to unblock > > libgdal-grass & qgis. libgdal-grass needs a source upload as usual. > > grass has been rebuilt on all release architectures too, qgis can be > rebuilt now. The binNMUs for qgis have also been scheduled. Cheers > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 > -- Sebastian Ramacher
Bug#992563: transition: gdal
On 9/9/21 5:57 AM, Sebastiaan Couwenberg wrote: > On 9/8/21 6:56 AM, Sebastiaan Couwenberg wrote: >> On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: >>> On 9/5/21 6:48 PM, Sebastian Ramacher wrote: On 2021-08-20 11:32:16 +0200, 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 > 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. Assuming that the version of pdal in experimental also builds fine against the new version of gdal, please go ahead and also start the pdal transition. >>> >>> PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to >>> unstable once gdal is built on all release architectures. The gdal >>> upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to >>> testing to fix #993334 there too. >> >> gdal has built on all release architectures, and pdal has been uploaded >> to unstable as well. > > Thanks for scheduling the binNMUs, please also binNMU grass to unblock > libgdal-grass & qgis. libgdal-grass needs a source upload as usual. grass has been rebuilt on all release architectures too, qgis can be rebuilt now. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 9/8/21 6:56 AM, Sebastiaan Couwenberg wrote: > On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: >> On 9/5/21 6:48 PM, Sebastian Ramacher wrote: >>> On 2021-08-20 11:32:16 +0200, 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 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. >>> >>> Assuming that the version of pdal in experimental also builds fine >>> against the new version of gdal, please go ahead and also start the pdal >>> transition. >> >> PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to >> unstable once gdal is built on all release architectures. The gdal >> upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to >> testing to fix #993334 there too. > > gdal has built on all release architectures, and pdal has been uploaded > to unstable as well. Thanks for scheduling the binNMUs, please also binNMU grass to unblock libgdal-grass & qgis. libgdal-grass needs a source upload as usual. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 9/7/21 3:07 PM, Sebastiaan Couwenberg wrote: > On 9/5/21 6:48 PM, Sebastian Ramacher wrote: >> On 2021-08-20 11:32:16 +0200, 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 >>> 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. >> >> Assuming that the version of pdal in experimental also builds fine >> against the new version of gdal, please go ahead and also start the pdal >> transition. > > PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to > unstable once gdal is built on all release architectures. The gdal > upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to > testing to fix #993334 there too. gdal has built on all release architectures, and pdal has been uploaded to unstable as well. Kind regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
On 9/5/21 6:48 PM, Sebastian Ramacher wrote: > On 2021-08-20 11:32:16 +0200, 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 >> 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. > > Assuming that the version of pdal in experimental also builds fine > against the new version of gdal, please go ahead and also start the pdal > transition. PDAL 2.3.0 also builds successfully with GDAL 3.3 so I'll upload that to unstable once gdal is built on all release architectures. The gdal upload to unstable had to wait a bit for 3.2.2+dfsg-3 to migrated to testing to fix #993334 there too. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#992563: transition: gdal
Control: tags -1 confirmed Control: tags 992358 confirmed On 2021-08-20 11:32:16 +0200, 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 > 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. Assuming that the version of pdal in experimental also builds fine against the new version of gdal, please go ahead and also start the pdal transition. Cheers > > > 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 > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#992563: 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 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
