Bug#1120361: transition: gdal
On 11/13/25 9:03 AM, Paul Gevers wrote:
On 11/13/25 05:32, Sebastiaan Couwenberg wrote:
The libgdal-grass autopkgtest needs gdal, grass, and libgdal-grass from unstable to pass:
https://ci.debian.net/packages/libg/libgdal-grass/testing/amd64/66167096/
Please schedule the jobs with the britney credentials to make it use those results.
I think I'm missing some detail here.
So depressing we have this discussion every gdal transition, see prior transitions:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110866#28
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086845#53
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070852#31
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055891#40
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038115#34
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023846#33
I really should just drop the autopkgtest as it's just a hindrance to testing migration as long as britney is doesn't know it should get all dependencies from unstable when testing packages involved in a transition.
I'm fully aware that the testing situation with transitions isn't ideal because normally in smooth transitions with co-installable libraries we're actually not testing the rebuilt binaries from unstable, but the old binaries in testing. In this case there seems to be something going on additionally, which isn't captured in package relations. libgdal-grass in testing is built against the old library of gdal (libgdal37), which is also installed in the testbed. So why would libgdal-grass complain? Is this the problem that during a transition within one stack both the new and old library are loaded and we're having a conflict that way and libgdal-grass is intelligent enough to prevent that? But as I see it there's only one library involved here, so where does that come from, the plugins?
The following packages come from unstable in the test:
gdal-data
gdal-plugins
libgdal38
python3-gdal
gdal-bin
libgdal37
Notice grass-core missing from that list.
See also README.source:
https://sources.debian.org/src/libgdal-grass/1%3A1.0.4-2/debian/README.source
Running the autopkgtest with grass from testing pulls in its old libgdal dependency, hence the need to also pull grass from unstable to have both grass & libgdal-grass using the same libgdal.
Paul
PS: libgdal37 is a rebuild in unstable that didn't migrate before the gdal transition.
And that's keeping the old armadillo in testing a few days longer.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: