On 11/19/23 08:54, Paul Gevers wrote:
On 19-11-2023 07:32, Sebastiaan Couwenberg wrote:
For the libgdal-grass autopkgtest to pass it needs to pull gdal,
grass, and libgdal-grass from unstable due to the tight coupling.
If it doesn't happen automatically and there is a tight coupling, where
is the tight coupling missing in the package relations?
britney only schedules:
gdal/3.8.0+dfsg-1
src:gdal from unstable
Likely because there is no new version for the libgdal-grass source
package, only a binNMU.
libgdal-grass (1:1.0.2-6+b1) has these dependencies to reflect the tight
coupling:
grass831 (provided by grass-core)
libgdal34 (>= 3.8.0)
grass-core in testing depends on the old libgdal33, hence the need to
also get grass and libgdal-grass from unstable when running autopkgtest
with gdal from unstable.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
