Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUrxX-0003PY-5Y for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 13 Nov 2019 12:41:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iUrxV-00077l-VP for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 13 Nov 2019 12:41:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUpHp-0001tt-4M for pgsql-pkg-debian@lists.postgresql.org; Wed, 13 Nov 2019 09:50:05 +0000 Received: from mail-pg1-x542.google.com ([2607:f8b0:4864:20::542]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iUpHj-0006DU-68 for pgsql-pkg-debian@lists.postgresql.org; Wed, 13 Nov 2019 09:50:03 +0000 Received: by mail-pg1-x542.google.com with SMTP id l24so1034276pgh.10 for ; Wed, 13 Nov 2019 01:49:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=f+QPYQ/lo4v4s62WbhctaqnJkXQaHss6QvCDVIhLrtI=; b=cVMkwP46MnSuve4KEbI+U71/ZE/0Hkbl7KfavzGiJO0YD3guaKUUj/9qVInz8E9vGS MdZxHEZyy1ghTYIc0Dv52ZKYlBKCmoTSaZn+TcjiwpnsFVwioTVwMHAo84TGrVzw84nQ ViN2DAZKo5cltAMblY0kxegimBgB/WU0cmrESGYwIdJ9Cp/6VyfxLNJZu+4kVHhw/GmZ tfWb78amDSggbh6AMJ6FnuO5P8TF/nR3ft2awt/nulNsdtGlSJvZORacpEd3GfX5EY/N IXoskje2mEuHKD2sUjdYMaqRvr/W1W9xD6+3Z3/YrpgA9G6IWyOzDSnr+BhEHRhaHLPb JmBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=f+QPYQ/lo4v4s62WbhctaqnJkXQaHss6QvCDVIhLrtI=; b=L2H90U2gW6v6dqu5rRXJROFz1oxsfHRX3H0mhiuyDeV1MXJrnr4IkglF34w3f9jrFS mnf/E/iRTS0/7MyBbQvdF3iVAkBj1MZny4RUSBvnAMZMH6MGMy6/+OJg5jROkx1EI+/v T+tt6nUjJzm0fDRnWc0FUCDvfmrwRTS/kegGFe8TvxuDaLeL2t43fYtPYmvF7UPgd4SV 7obQPTNOimfchzXGvBqHo64PAVKxJow2Wcldkin4olfMivYQYpvCsS8QY2C1K9erP2Wb QGebpUp1+gc7HXSDqgBFo4wd3qKSZ9AciO4K7lv6udhazw+56ae3XNFG0UfvMnVe6Na0 SzOw== X-Gm-Message-State: APjAAAVvEp2sxkqecuD0CW5qTkA4h7rmrtqgrPrSDMmM4dVnlO8sMjiv zfkDJwKXm/qpBfbB3ForY+5cBV8U3qRiXu1wVmA= X-Google-Smtp-Source: APXvYqyCEpa7Zsen/Mj/BZg37lGkxi8rzYdICs05FhwOY4g3J/iqyPGyiIxAuX5/qrdnZscJTA1th6eyGBXxoiMxn6A= X-Received: by 2002:a17:90a:3d01:: with SMTP id h1mr3714941pjc.15.1573638597856; Wed, 13 Nov 2019 01:49:57 -0800 (PST) MIME-Version: 1.0 References: <20191112143958.GC20731@msg.df7cb.de> In-Reply-To: <20191112143958.GC20731@msg.df7cb.de> From: =?UTF-8?Q?Michael_B=C3=B6hm?= Date: Wed, 13 Nov 2019 10:49:46 +0100 Message-ID: Subject: Re: postgis update from 2.5 to 3 To: Christoph Berg Cc: pgsql-pkg-debian@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000a154340597374999" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000a154340597374999 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Di., 12. Nov. 2019 um 15:39 Uhr schrieb Christoph Berg = : > Re: Michael B=C3=B6hm 2019-11-12 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 t= he > > package "postgresql-10-postgis-3-scripts" tries to overwrite some files > > already provided by " postgresql-10-postgis-2.5-scripts": > > > > =C2=BB/usr/share/postgresql/10/applications/shp2pgsql-gui.desktop=C2=AB > > =C2=BB/usr/share/postgresql/10/icons/hicolor/16x16/apps/shp2pgsql-gui.p= ng=C2=AB > > 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. > Well it looked like this: edugis=3D# SELECT PostGIS_full_version(); FEHLER: konnte nicht auf Datei =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: = Datei oder Verzeichnis nicht gefunden KONTEXT: SQL-Anweisung =C2=BBSELECT public.postgis_lib_version()=C2=AB PL/pgSQL-Funktion postgis_full_version() Zeile 26 bei SQL-Anweisung edugis=3D# ALTER EXTENSION postgis UPDATE; WARNUNG: unpackaging raster WARNUNG: PostGIS Raster functionality has been unpackaged TIP: type `SELECT postgis_extensions_upgrade(); to finish the upgrade. After upgrading, if you want to drop raster, run: DROP EXTENSION postgis_raster; FEHLER: konnte nicht auf Datei =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: = Datei oder Verzeichnis nicht gefunden KONTEXT: PL/pgSQL-Funktion _postgis_drop_function_if_needed(text,text) Zeile 6 bei FOR =C3=BCber SELECT-Zeilen edugis=3D# SELECT PostGIS_Extensions_Upgrade(); WARNUNG: unpackaging raster WARNUNG: PostGIS Raster functionality has been unpackaged TIP: type `SELECT postgis_extensions_upgrade(); to finish the upgrade. After upgrading, if you want to drop raster, run: DROP EXTENSION postgis_raster; FEHLER: konnte nicht auf Datei =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: = Datei oder Verzeichnis nicht gefunden KONTEXT: PL/pgSQL-Funktion _postgis_drop_function_if_needed(text,text) Zeile 6 bei FOR =C3=BCber SELECT-Zeilen SQL-Anweisung =C2=BBALTER EXTENSION postgis UPDATE TO "3.0.0";=C2=AB PL/pgSQL-Funktion postgis_extensions_upgrade() Zeile 22 bei EXECUTE edugis=3D# DROP EXTENSION postgis_raster; FEHLER: Erweiterung =C2=BBpostgis_raster=C2=AB existiert nicht edugis=3D# SELECT PostGIS_full_version(); FEHLER: konnte nicht auf Datei =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: = Datei oder Verzeichnis nicht gefunden KONTEXT: SQL-Anweisung =C2=BBSELECT public.postgis_lib_version()=C2=AB PL/pgSQL-Funktion postgis_full_version() Zeile 26 bei SQL-Anweisung After that i reverted to the snapshot i made before and tried option 2. > > 2. Installing postgis-3(-scripts) with "-o > > Dpkg::Options::=3D"--force-overwrite"" was successful and i could finis= h > 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 u= p? > > 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? > Well i always try to update asap so before i had: ii postgresql-10-postgis-2.5 2.5.3+dfsg-2.pgdg100+1 ii postgresql-10-postgis-2.5-scripts 2.5.3+dfsg-2.pgdg100+1 and now ii postgresql-10-postgis-3 3.0.0+dfsg-2~exp1.pgdg100+1 ii postgresql-10-postgis-3-scripts 3.0.0+dfsg-2~exp1.pgdg100+1 > > Thanks for reporting, > Christoph > No problem, if i need to find a workaround for myself and nothing comes up from the depth of the web i like to somehow let people know. --000000000000a154340597374999 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Am Di., 12. Nov. 2019 um 15:39=C2=A0Uhr s= chrieb Christoph Berg <myon@debian.or= g>:
Re: Michael B=C3=B6hm 2019-11-12 <CAKJYtEQVW=3DV3wG9wX4nBoX9Rqti3PfJ7qANNdjO5ztF_3JyZSA@mail.gmail.com&= gt;
> 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": >
> =C2=BB/usr/share/postgresql/10/applications/shp2pgsql-gui.desktop=C2= =AB
> =C2=BB/usr/share/postgresql/10/icons/hicolor/16x16/apps/shp2pgsql-gui.= png=C2=AB

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

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

Interesting... I would have thought that upgrading didn't need the old<= br> files.

Well it looked like this:
<= div>
edugis=3D# SELECT PostGIS_full_version();
FEHLER: =C2= =A0konnte nicht auf Datei =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: Datei = oder Verzeichnis nicht gefunden
KONTEXT: =C2=A0SQL-Anweisung =C2=BBSELEC= T public.postgis_lib_version()=C2=AB
PL/pgSQL-Funktion postgis_full_vers= ion() Zeile 26 bei SQL-Anweisung

edugis=3D# ALTER EXTENSI= ON postgis UPDATE;
WARNUNG: =C2=A0unpackaging raster
WARNUNG: =C2=A0P= ostGIS Raster functionality has been unpackaged
TIP: =C2=A0type `SELECT = postgis_extensions_upgrade(); to finish the upgrade. After upgrading, if yo= u want to drop raster, run: DROP EXTENSION postgis_raster;
FEHLER: =C2= =A0konnte nicht auf Datei =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: Datei = oder Verzeichnis nicht gefunden
KONTEXT: =C2=A0PL/pgSQL-Funktion _postgi= s_drop_function_if_needed(text,text) Zeile 6 bei FOR =C3=BCber SELECT-Zeile= n

edugis=3D# SELECT PostGIS_Extensions_Upgrade();
WARN= UNG: =C2=A0unpackaging raster
WARNUNG: =C2=A0PostGIS Raster functionalit= y has been unpackaged
TIP: =C2=A0type `SELECT postgis_extensions_upgrade= (); to finish the upgrade. After upgrading, if you want to drop raster, run= : DROP EXTENSION postgis_raster;
FEHLER: =C2=A0konnte nicht auf Datei = =C2=BB$libdir/postgis-2.5=C2=AB zugreifen: Datei oder Verzeichnis nicht gef= unden
KONTEXT: =C2=A0PL/pgSQL-Funktion _postgis_drop_function_if_needed(= text,text) Zeile 6 bei FOR =C3=BCber SELECT-Zeilen
SQL-Anweisung =C2=BBA= LTER EXTENSION postgis UPDATE TO "3.0.0";=C2=AB
PL/pgSQL-Funkt= ion postgis_extensions_upgrade() Zeile 22 bei EXECUTE

edu= gis=3D# DROP EXTENSION postgis_raster;
FEHLER: =C2=A0Erweiterung =C2=BBp= ostgis_raster=C2=AB existiert nicht

edugis=3D# SELECT Pos= tGIS_full_version();
FEHLER: =C2=A0konnte nicht auf Datei =C2=BB$libdir/= postgis-2.5=C2=AB zugreifen: Datei oder Verzeichnis nicht gefunden
KONTE= XT: =C2=A0SQL-Anweisung =C2=BBSELECT public.postgis_lib_version()=C2=AB
= PL/pgSQL-Funktion postgis_full_version() Zeile 26 bei SQL-Anweisung

=
After that i reverted to the snapshot i made before and tried op= tion 2.
=C2=A0
> 2. Installing postgis-3(-scripts) with "-o
> Dpkg::Options::=3D"--force-overwrite"" was successful a= nd i could finish the
> upgrade with "ALTER EXTENSION postgis UPDATE;" and "SEL= ECT
> 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?

Well i always try to update asap so before i had:<= /div>
ii =C2=A0postgresql-10-postgis-2.5 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A02.5.3+dfsg-2.pgdg100+1
ii =C2=A0postgresql-10-postgis-2.5-s= cripts =C2=A0 =C2=A02.5.3+dfsg-2.pgdg100+1
and now
<= div>ii =C2=A0postgresql-10-postgis-3 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A03.0.0+dfsg-2~exp1.pgdg100+1
ii =C2=A0postgresql-10-postgis-3-s= cripts =C2=A0 =C2=A0 =C2=A03.0.0+dfsg-2~exp1.pgdg100+1
=C2=A0=

Thanks for reporting,
Christoph

No problem, if i need to find= a workaround for myself and nothing comes up from the depth of the web i l= ike to somehow let people know.
--000000000000a154340597374999--