AW: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1

From: Marco Lechner <mlechner(at)bfs(dot)de>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: AW: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1
Date: 2020-07-15 10:34:58
Message-ID: 65a9ad243eca4fd8b22a011f30decc1e@bfs.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

OK, now I got it.
Thnx

Marco

Von: Magnus Hagander [mailto:magnus(at)hagander(dot)net]
Gesendet: Mittwoch, 15. Juli 2020 10:49
An: Marco Lechner <mlechner(at)bfs(dot)de>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Betreff: Re: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1

proj7 is in the PostgreSQL repo, in pgdg-common. Just a "yum install postgis30_12" brings it in automatically for me.

If you don't have that one, then your repo config may be out of date per https://www.postgresql.org/about/news/2027/.

//Magnus

On Wed, Jul 15, 2020 at 10:44 AM Marco Lechner <mlechner(at)bfs(dot)de<mailto:mlechner(at)bfs(dot)de>> wrote:
But how about the proj7 dependency?

Marco

Von: Magnus Hagander [mailto:magnus(at)hagander(dot)net<mailto:magnus(at)hagander(dot)net>]
Gesendet: Mittwoch, 15. Juli 2020 10:34
An: Marco Lechner <mlechner(at)bfs(dot)de<mailto:mlechner(at)bfs(dot)de>>; PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org<mailto:pgsql-bugs(at)lists(dot)postgresql(dot)org>>
Betreff: Re: BUG #16543: Package conflicts due to missing llvm-toolset-7-clang >= 4.0.1 and proj70 >= 7.0.1

On Wed, Jul 15, 2020 at 10:15 AM PG Bug reporting form <noreply(at)postgresql(dot)org<mailto:noreply(at)postgresql(dot)org>> wrote:
The following bug has been logged on the website:

Bug reference: 16543
Logged by: Marco Lechner
Email address: mlechner(at)bfs(dot)de<mailto:mlechner(at)bfs(dot)de>
PostgreSQL version: 12.3
Operating system: RHEL7/OEL7
Description:

As dicussed in pgsql-general on May 28th there are package conflicts when
updating postgresql12 with postgis30:
...
at the moment we are facing similar conflicts on Oracle LInux 7 (wich is
derived from RHEL) – we manage our machines using Spacewalk. The conflicts
occur (as expected) on Spacewalk as well as on manually using yum:

Fehler: Paket: postgresql11-devel-11.8-1PGDG.rhel7.x86_64
(oraclelinux7postgresql11)
Benötigt: llvm-toolset-7-clang >= 4.0.1
Fehler: Paket: postgis30_12-3.0.1-5.rhel7.x86_64
(oraclelinux7postgresql12)
Benötigt: proj70 >= 7.0.1
Installiert: proj70-7.0.0-2.rhel7.x86_64
(@oraclelinux7postgresql11)
proj70 = 7.0.0-2.rhel7
Verfügbar: proj70-7.0.0-1.rhel7.x86_64
(oraclelinux7postgresql11)
proj70 = 7.0.0-1.rhel7
Fehler: Paket: postgresql12-devel-12.3-1PGDG.rhel7.x86_64
(oraclelinux7postgresql12)
Benötigt: llvm-toolset-7-clang >= 4.0.1
...

llvm-toolset is needed by postgresql11-devel and postgresql12-devel in this setup it seems, but why do you need those? If what you want is Postgis, then the postgis RPM should be enough and that shouldn't need devel packages at all, and therefore not the llvm packages.

If you do actually need the devel packages, you need to enable the scl repo. On centos, that means install centos-release-scl. On RHEL, I believe you do "yum-config-manager --enable rhel-server-rhscl-7-rpms".
But again,if "all" you want is PostGIS, they shouldn't be needed.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Arthur Nascimento 2020-07-15 12:52:37 Re: BUG #16542: High CPU Usage
Previous Message Dmitry Dolgov 2020-07-15 10:03:33 Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table