[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#989597: marked as done (release.debian.org: upgrade issue: non-coinstallability of libgdal20 and libgdal28)

Your message dated Sun, 27 Jun 2021 16:13:28 +0200
with message-id <YNiHiAFIqL4HHK77@ramacher.at>
and subject line Re: Bug#989597: release.debian.org: upgrade issue: non-coinstallability of libgdal20 and libgdal28
has caused the Debian Bug report #989597,
regarding release.debian.org: upgrade issue: non-coinstallability of libgdal20 and libgdal28
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
989597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989597
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal

Let's start with the debian-release@ discussion here, this may be turned
into an unblock request later. 

On Tue, 18 May 2021 20:36:23 +0200 Dennis Filder <d.filder@web.de> wrote:
> One more observation: Bullseye's gdal-data 3.2.1+dfsg-1 defines a
> Breaks: libgdal20 (< 2.5.0~), but the libgdal20 in Buster is 2.4.0,
> and postgresql-11-postgis-2.5 depends on that.  libgdal28 depends on
> gdal-data (>=3.2.1+dfsg-1).  To me it looks like there's no way to
> keep postgresql-11-postgis-2.5 around if anything that depends on
> libgdal28 (postgis, libopencv-imgcodecs4.5, ...) gets installed.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988722#31

gdal can rename gdal-data to gdal3-data, build with
--datadir=/sur/share/gdal3 and drop the Breaks on libgdal20.
Thus libgdal20 + gdal-data from buster should be co-installable with
libgdal28 + gdal3-data from bullseye and survive the upgrade if needed.

A patch doing this is attached, I'm now testing the upgrade paths
(along the introduction of the libhdf5*-103 metapackages).

A good gdal bug to reuse would be #986975

Updating gdal may be a bit more tricky, because testing has 3.2.1 while
sid has 3.2.2.


Andreas

diff -Nru gdal-3.2.1+dfsg/debian/changelog gdal-3.2.1+dfsg/debian/changelog
--- gdal-3.2.1+dfsg/debian/changelog	2021-01-04 13:49:29.000000000 +0100
+++ gdal-3.2.1+dfsg/debian/changelog	2021-06-07 09:02:51.000000000 +0200
@@ -1,3 +1,12 @@
+gdal (3.2.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename gdal-data to gdal3-data and build with --datadir=/usr/share/gdal3.
+    This is a workaround for upgrade issues caused by libgdal20 (in buster)
+    and libgdal28 (in bullseye) not being co-installable.  (Closes: #xxxxxx)
+
+ -- Andreas Beckmann <anbe@debian.org>  Mon, 07 Jun 2021 09:02:51 +0200
+
 gdal (3.2.1+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru gdal-3.2.1+dfsg/debian/control gdal-3.2.1+dfsg/debian/control
--- gdal-3.2.1+dfsg/debian/control	2021-01-04 13:44:44.000000000 +0100
+++ gdal-3.2.1+dfsg/debian/control	2021-06-07 09:02:51.000000000 +0200
@@ -68,7 +68,7 @@
 Package: libgdal28
 Architecture: any
 Section: libs
-Depends: gdal-data (>= ${source:Version}),
+Depends: gdal3-data (>= ${source:Version}),
          ${shlibs:Depends},
          ${misc:Depends}
 Recommends: proj-bin
@@ -189,11 +189,10 @@
  namely gdal_translate, gdalinfo, gdaladdo, gdalwarp, ogr2ogr, ogrinfo,
  ogrtindex.
 
-Package: gdal-data
+Package: gdal3-data
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends}
-Breaks: libgdal20 (<< 2.5.0~)
 Description: Geospatial Data Abstraction Library - Data files
  GDAL is a translator library for raster geospatial data formats.
  As a library, it presents a single abstract data model to the
diff -Nru gdal-3.2.1+dfsg/debian/gdal-data.install gdal-3.2.1+dfsg/debian/gdal-data.install
--- gdal-3.2.1+dfsg/debian/gdal-data.install	2020-10-20 05:44:12.000000000 +0200
+++ gdal-3.2.1+dfsg/debian/gdal-data.install	1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-usr/share/gdal
diff -Nru gdal-3.2.1+dfsg/debian/gdal-data.lintian-overrides gdal-3.2.1+dfsg/debian/gdal-data.lintian-overrides
--- gdal-3.2.1+dfsg/debian/gdal-data.lintian-overrides	2020-10-24 06:58:20.000000000 +0200
+++ gdal-3.2.1+dfsg/debian/gdal-data.lintian-overrides	1970-01-01 01:00:00.000000000 +0100
@@ -1,6 +0,0 @@
-# Not a problem
-national-encoding usr/share/gdal/s57expectedinput.csv
-
-# Not documentation
-package-contains-documentation-outside-usr-share-doc usr/share/gdal/pci_*.txt
-
diff -Nru gdal-3.2.1+dfsg/debian/gdal3-data.install gdal-3.2.1+dfsg/debian/gdal3-data.install
--- gdal-3.2.1+dfsg/debian/gdal3-data.install	1970-01-01 01:00:00.000000000 +0100
+++ gdal-3.2.1+dfsg/debian/gdal3-data.install	2021-06-07 09:02:01.000000000 +0200
@@ -0,0 +1 @@
+usr/share/gdal3
diff -Nru gdal-3.2.1+dfsg/debian/gdal3-data.lintian-overrides gdal-3.2.1+dfsg/debian/gdal3-data.lintian-overrides
--- gdal-3.2.1+dfsg/debian/gdal3-data.lintian-overrides	1970-01-01 01:00:00.000000000 +0100
+++ gdal-3.2.1+dfsg/debian/gdal3-data.lintian-overrides	2021-06-07 09:01:48.000000000 +0200
@@ -0,0 +1,6 @@
+# Not a problem
+national-encoding usr/share/gdal3/s57expectedinput.csv
+
+# Not documentation
+package-contains-documentation-outside-usr-share-doc usr/share/gdal3/pci_*.txt
+
diff -Nru gdal-3.2.1+dfsg/debian/rules gdal-3.2.1+dfsg/debian/rules
--- gdal-3.2.1+dfsg/debian/rules	2021-01-04 13:44:33.000000000 +0100
+++ gdal-3.2.1+dfsg/debian/rules	2021-06-07 09:02:46.000000000 +0200
@@ -117,6 +117,7 @@
 override_dh_auto_configure:
 	for V in $(PYVERS); do \
 		PYTHON=/usr/bin/python$$V ./configure --prefix=/usr \
+			--datadir=\$$\{prefix\}/share/gdal3 \
 			--mandir=\$$\{prefix\}/share/man \
 			--includedir=\$$\{prefix\}/include/gdal \
 			--with-hide-internal-symbols=yes \

--- End Message ---
--- Begin Message --- 
On 2021-06-21 20:40:01 +0200, Sebastian Ramacher wrote:
> On 2021-06-18 17:42:44 +0200, Sebastiaan Couwenberg wrote:
> > On 6/18/21 5:19 PM, Andreas Beckmann wrote:
> > > On 18/06/2021 09.50, Sebastiaan Couwenberg wrote:
> > >> I'm increasingly in favor of removing the Breaks from gdal-data, the
> > >> attached procedure works for me in buster chroot.
> > > 
> > >> There is much less need for gdal-data breaking libgdal20 for us than
> > >> there is in the UbuntuGIS PPA use case. I'm not aware of any packages
> > >> that use gdal in the maintainer scripts that would be using the old gdal
> > >> on their removal. So there shouldn't be any actual expected breakage.
> > > 
> > > Do you have some ideas what could break by installing gdal-data 3.x in
> > > buster?
> > 
> > qgis crssync is a likely candidate, prior to PROJ 6 it relied more more
> > heavily on the projection data included in gdal.
> > 
> > Other than that I don't know. You'd have to grep through the sources to
> > find the functions using those files, and then search through reverse
> > dependencies for use of those functions.
> > 
> > > I.e. on a partial upgrade. (Could someone run autopkgtests in
> > > buster with the proposed gdal-data?)
> > 
> > Many of the gdal rdeps don't have autopkgtests, and the most prominents
> > ones don't.
> > 
> > >> This change is minimal, doesn't require NEW packages, nor introduces
> > >> divergence from upstream (as when the files would be moved to
> > >> u/s/gdal/<X.Y> in libgdal28), hence it's my preferred solution.
> > > 
> > > That's a bad upstream decision, but as you described them, they don't
> > > care about upgrade paths :-(
> > 
> > PostGIS upstream are the ones who don't particular care about
> > distribution upgrades. GDAL upstream is actually quite good (and
> > responsible for the bulk of the work that went into PROJ 6).
> > 
> > >> If there is no objection, I'll upload gdal (3.2.2+dfsg-2) with the
> > >> changes from the debdiff to unstable.
> > > 
> > > Sounds fine to me.
> > 
> > If the RMs are onboard as well, then let's not waste any more time on
> > alternatives.
> 
> It's a step in the right direction. So, yes, please go ahead.

glad migrated, so let's close this bug report.

Cheers

> 
> Cheers
> 
> > 
> > Kind Regards,
> > 
> > Bas
> > 
> > -- 
> >  GPG Key ID: 4096R/6750F10AE88D4AF1
> > Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
> > 
> 
> -- 
> Sebastian Ramacher



-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: