On 6/14/21 9:29 AM, Andreas Beckmann wrote: > On 13/06/2021 23.44, Sebastian Ramacher wrote: >> On 2021-06-13 23:35:40 +0200, Andreas Beckmann wrote: >>> On 13/06/2021 22.44, Sebastian Ramacher wrote: >>>> My goal is to make libgdal20 and libgdal28 co-installable. Adding those >>>> Breaks is not enough and is step into the wrong direction. >>> >>> Thanks for making that clear. I'll think again about libogdi ... >> >> libogdi4.1 was partially fixed. It only needs the Breaks+Replaces >> removed. See 989795 > > I did some quick tests with the B+R removed, hdf5 patched to build the > transitional packages and gdal patched to produce gdal3-data: we have > finally achieved libgdal20/libgdal28 co-installability ;-)
That's nice, but I don't want to maintain a version specific gdal-data package. postgis by itself is not interesting, its only contains commandline tools. postgresql-11-postgis-2.5 is the package which contains the postgresql extension. That (also) get removed during the `apt upgrade` from buster to bullseye. I don't particularly care about having libgdal20 & libgdal28 co-installable for postgis datavase upgrades with pg_upgradecluster. That has never been supported. What actual problems do are solved by making them co-installable? So far the only actualy problem that has been identified is the need for `apt full-upgrade` twice when the Breaks/Replaces on libgdal20 is not present. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1