Hi,
I tired installing the single package but still the same error
yum install -y postgis33_15-client-3.3.5-1PGDG.rhel8.x86_64.rpm
> Last metadata expiration check: 0:01:18 ago on Wed 21 Feb 2024 02:51:19 AM
> UTC.
> Dependencies resolved.
>
> ==============================================================================================================================================================================================================================
> Package Architecture
> Version
> Repository Size
>
> ==============================================================================================================================================================================================================================
> Installing:
> postgis33_15-client x86_64
> 3.3.5-1PGDG.rhel8
> @commandline 289 k
> Transaction Summary
>
> ==============================================================================================================================================================================================================================
> Install 1 Package
> Total size: 289 k
> Installed size: 1.4 M
> Downloading Packages:
> Running transaction check
> Transaction check succeeded.
> Running transaction test
> Error: Transaction test error:
> file /usr/lib/.build-id/b6/89201f4430759c8544cd168dc6ba3e24f7d912 from
> install of postgis33_15-client-3.3.5-1PGDG.rhel8.x86_64 conflicts with file
> from package postgis33_13-client-3.3.5-1PGDG.rhel8.x86_64
Alternatively just remove the postgis_33_13_client
-- Will this create a problem with the existing installation of PostGIS?.
I am asking because we are just installing the new packages for now and we
will do the actual postgres upgrade during a downtime window
Thanks,
Nikhil
On Tue, Feb 20, 2024 at 11:30 PM Regina Obe <l...@pcorp.us> wrote:
> I’m guessing you can’t have both clients installed. Not sure what is in
> the client package.
>
>
>
> What if you don’t do
>
>
>
> yum install -y postgis_33_15*
>
>
>
> But instead just
>
>
>
> yum install -y postgis_33_15
>
>
>
> I’m guessing whatever that client is, they probably get installed in the
> same place, so you only need one of them.
>
>
>
> Alternatively just remove the postgis_33_13_client
>
>
>
> *From:* Nikhil Shetty <nikhil.db...@gmail.com>
> *Sent:* Tuesday, February 20, 2024 12:07 PM
> *To:* Regina Obe <l...@pcorp.us>
> *Cc:* PostGIS Users Discussion <postgis-users@lists.osgeo.org>
> *Subject:* Re: GDAL dependencies during PostGIS upgrade
>
>
>
> Hi Regina,
>
>
>
> I upgraded the existing PostGIS 3.1.2 to 3.3.5 on PG13 but now when I am
> trying to install PostGIS 3.3.5 for PG15 , I am getting below error
>
>
>
> Error: Transaction test error:
>
> file /usr/lib/.build-id/b6/89201f4430759c8544cd168dc6ba3e24f7d912 from
> install of postgis33_15-client-3.3.5-1PGDG.rhel8.x86_64 conflicts with file
> from package postgis33_13-client-3.3.5-1PGDG.rhel8.x86_64
>
>
>
> Do you know how we can resolve this ?
>
>
>
>
>
> Complete install o/p
>
>
>
> yum install -y postgis33_15*
> Last metadata expiration check: 0:01:21 ago on Tue 20 Feb 2024 05:01:03 PM
> UTC.
> Dependencies resolved.
>
> ==============================================================================================================================================================================================================================
> Package Architecture
> Version
> Repository Size
>
> ==============================================================================================================================================================================================================================
> Installing:
> postgis33_15 x86_64
> 3.3.5-1PGDG.rhel8
> @commandline 4.8 M
> postgis33_15-client x86_64
> 3.3.5-1PGDG.rhel8
> @commandline 289 k
> postgis33_15-devel x86_64
> 3.3.5-1PGDG.rhel8
> @commandline 8.3 k
> postgis33_15-utils x86_64
> 3.3.5-1PGDG.rhel8
> @commandline 44 k
> Transaction Summary
>
> ==============================================================================================================================================================================================================================
> Install 4 Packages
> Total size: 5.1 M
> Installed size: 45 M
> Downloading Packages:
> Running transaction check
> Transaction check succeeded.
> Running transaction test
> Error: Transaction test error:
> file /usr/lib/.build-id/b6/89201f4430759c8544cd168dc6ba3e24f7d912 from
> install of postgis33_15-client-3.3.5-1PGDG.rhel8.x86_64 conflicts with file
> from package postgis33_13-client-3.3.5-1PGDG.rhel8.x86_64
>
>
>
> Thanks,
>
> Nikhil
>
>
>
> On Fri, Feb 16, 2024 at 11:16 AM Nikhil Shetty <nikhil.db...@gmail.com>
> wrote:
>
> Hi Regina,
>
>
>
> We are upgrading from PG 13 3.1.2 to PG 15 3.3.5
>
>
>
> I forget if pg_upgrade checks the old .so to see if it can still load it
> or if it only checks if the new .so it is expecting in the new cluster is
> still available.
>
> pg_upgrade is checking in the PG13 lib whether the .so file exists or not.
>
>
>
> If it does check, I’d try upgrading to a newer PostGIS on your older
> cluster, doesn’t need to be the same, just one where the gdals are
> compatible.
>
> We might have to go with this approach because it checks the .so file in
> old version
>
>
>
>
>
> Error:
>
> pg_dump: error: query failed: ERROR: could not access file
> "$libdir/postgis-3": No such file or directory
>
> pg_dump: detail: Query was: EXECUTE dumpFunc('23873')
>
>
>
>
>
> Missing .so files:
>
>
>
> -0-root@host:/usr/pgsql-13/lib # ls -l /usr/pgsql-13/lib/postgis*
>
> ls: cannot access '/usr/pgsql-13/lib/postgis*': No such file or directory
>
>
>
> -2-root@host:/usr/pgsql-13/lib # ls -l /usr/pgsql-15/lib/postgis*
>
> /usr/pgsql-15/lib/postgis-3.so
>
> /usr/pgsql-15/lib/postgis_raster-3.so
>
> /usr/pgsql-15/lib/postgis_sfcgal-3.so
>
> /usr/pgsql-15/lib/postgis_topology-3.so
>
>
>
> Thanks,
>
> Nikhil
>
>
>
> On Fri, Feb 16, 2024 at 10:53 AM Regina Obe <l...@pcorp.us> wrote:
>
> Nikhil,
>
>
>
> Which version of PostgreSQL are you upgrading from.
>
>
>
> I forget if pg_upgrade checks the old .so to see if it can still load it
> or if it only checks if the new .so it is expecting in the new cluster is
> still available.
>
>
>
> If it doesn’t check the old to try to load the lib, dropping postgis-3.1.2
> should work just fine.
>
> Since 3.0, the .so file didn’t change, so pg_upgrading from say a PG 13
> 3.1.2 to a PG 15 3.3.5 should work just fine.
>
>
>
> If it does check, I’d try upgrading to a newer PostGIS on your older
> cluster, doesn’t need to be the same, just one where the gdals are
> compatible.
>
>
>
> *From:* Nikhil Shetty <nikhil.db...@gmail.com>
> *Sent:* Thursday, February 15, 2024 11:37 PM
> *To:* PostGIS Users Discussion <postgis-users@lists.osgeo.org>
> *Subject:* GDAL dependencies during PostGIS upgrade
>
>
>
> Hi Team,
>
>
>
> We are planning to upgrade postgres to 15 and postgis from 3.1.2 to 3.3.5.
>
>
>
> While installing postgis 3.3.5 we found some dependency issues with
> gdal36, we were able to workaround by removing postgis 3.1.2 and gdal32
> packages but for postgres upgrade we need both postgis (3.1.2 and 3.3.5)
> packages to be present.
>
>
>
> Below is the issue when installing gdal36 which is required for postgis
> 3.3.5
>
>
>
> -0-root@<host1>:/tmp # yum install
> gdal36-libs-3.6.4-6PGDG.rhel8.x86_64.rpm
> Last metadata expiration check: 0:00:58 ago on Wed 31 Jan 2024 02:01:35 PM
> UTC.
> Error:
> Problem: problem with installed package gdal32-libs-3.2.3-1.rhel8.x86_64
> - package gdal32-libs-3.2.3-1.rhel8.x86_64 requires
> libarmadillo.so.9()(64bit), but none of the providers can be installed
> - package gdal32-libs-3.2.2-13.rhel8.x86_64 requires
> libarmadillo.so.9()(64bit), but none of the providers can be installed
> - cannot install both armadillo-12.6.6-1.el8.x86_64 and
> armadillo-9.700.2-1.el8.x86_64
> - cannot install both armadillo-9.700.2-1.el8.x86_64 and
> armadillo-12.6.6-1.el8.x86_64
> - package gdal36-libs-3.6.4-6PGDG.rhel8.x86_64 requires
> libarmadillo.so.12()(64bit), but none of the providers can be installed
> - conflicting requests
> (try to add '—allowerasing' to command line to replace conflicting
> packages or '—skip-broken' to skip uninstallable packages or '—nobest' to
> use not only best candidate packages)
>
>
>
>
>
> Thanks,
>
> Nikhil
>
>
