Date: Tue, 12 Nov 2019 15:39:58 +0100
From: Christoph Berg <myon@debian.org>
To: Michael =?iso-8859-1?Q?B=F6hm?= <dudleyperkins@gmail.com>
Cc: pgsql-pkg-debian@lists.postgresql.org
Subject: Re: postgis update from 2.5 to 3
Message-ID: <20191112143958.GC20731@msg.df7cb.de>
References: 
 <CAKJYtEQVW=V3wG9wX4nBoX9Rqti3PfJ7qANNdjO5ztF_3JyZSA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKJYtEQVW=V3wG9wX4nBoX9Rqti3PfJ7qANNdjO5ztF_3JyZSA@mail.gmail.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
Precedence: bulk

Re: Michael Böhm 2019-11-12 <CAKJYtEQVW=V3wG9wX4nBoX9Rqti3PfJ7qANNdjO5ztF_3JyZSA@mail.gmail.com>
> As always i wanted to install the newer version beside the current one and
> then do the extension upgrade in postgres. Problem is that installing the
> package "postgresql-10-postgis-3-scripts" tries to overwrite some files
> already provided by " postgresql-10-postgis-2.5-scripts":
> 
> »/usr/share/postgresql/10/applications/shp2pgsql-gui.desktop«
> »/usr/share/postgresql/10/icons/hicolor/16x16/apps/shp2pgsql-gui.png«

Meh. PostGIS installs files in way too many weird places.

> 1. Removing all 2.5-packages, then installing 3 was one solution, but
> "ALTER EXTENSION postgis UPDATE;" afterwards wasn't possible as it
> complained about the missing 2.5-scripts-folder

Interesting... I would have thought that upgrading didn't need the old
files.

> 2. Installing postgis-3(-scripts) with "-o
> Dpkg::Options::="--force-overwrite"" was successful and i could finish the
> upgrade with "ALTER EXTENSION postgis UPDATE;" and "SELECT
> PostGIS_Extensions_Upgrade();"

That's the workaround I would have suggested, yes.

> Is this a packaging-bug, everything working as expected or did i mess up?

Packaging bug. I thought I had tested that, but apparently I had
tested something else. I wonder how I missed that given that
postgresql-10-postgis-3 does depend on postgresql-10-postgis-3-scripts
now, and same for the -2.5 packages. Maybe the problem is only with
older packages.

Which versions of the -2.5 and -3 packages exactly did you use?

Thanks for reporting,
Christoph