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
