On 9/2/19 11:12 AM, Sebastiaan Couwenberg wrote: > On 9/2/19 10:43 AM, Emilio Pozuelo Monfort wrote: >> There's also an autopkgtest regression for r-cran-sf as you can see in the >> excuses at https://packages.qa.debian.org/p/proj.html. That's blocking proj >> from >> being a migration candidate. > > That's why I filed #939002. > > There is also the autopkgtest failure of pyresample (python-pyproj rdep) > for which #939128 was filed. For this I'm considering moving proj 5.2.0 > & pyproj 2.3.1 from experimental to unstable if these autopkgtest > failure keep blocking the testing migration for more than a week.
The pyresample autopkgtest failure is fixed with proj 6.2.0-1 & python-pyproj 2.3.1+ds-1 in unstable. Do we have to wait for testing autoremoval of r-cran-sf or can one of you hint it out? If you want to get this transition done to start the perl transition, several packages in this transition also need aging: * proj * python-pyproj * osm2pgsql * mapnik * openorienteering-mapper * qgis * vtk6 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
