Bug#986975: libgdal28: please add Breaks: libgdal20

Sebastiaan Couwenberg sebastic at xs4all.nl
Wed May 19 17:49:10 BST 2021


On 5/19/21 6:21 PM, Dennis Filder wrote:
> Do you remember why you added that Breaks:? 

Because files in gdal-data (>= 2.5.0~) cannot be used by libgdal20 (<<
2.5.0~). GDAL 2.5.0~beta1 introduced PROJ 6 support, which changed the
content of proj-data significantly, making it incompatible with prior
versions.

This issue affected Ubuntu bionic where the newer GDAL is available via
the UbuntuGIS PPA.

> And if it was due to
> upstream changes does that mean that postgis-enabled clusters are
> essentially unmigratable unless you dump them in full before starting
> the upgrade?  Because if so, this should be mentioned in the Bullseye
> release notes.

PostGIS databases have never been able to be migrated during a
distribution upgrade. You've always needed to recreate the databases in
the new cluster.

With the PostGIS library no longer including the minor version in its
filename since 3.0, it might be possible to migrate PostGIS databases
with pg_upgradecluster from bullseye to bookworm if PostGIS 3.x will be
in bookworm too.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



More information about the Pkg-grass-devel mailing list