Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlvSi-004tfY-Bm for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 28 Sep 2023 18:10:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlvSh-00FDQf-3M for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 28 Sep 2023 18:10:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlvSg-00FDQW-7q for pgsql-pkg-yum@lists.postgresql.org; Thu, 28 Sep 2023 18:10:06 +0000 Received: from mail-yw1-x1132.google.com ([2607:f8b0:4864:20::1132]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qlvSa-0079uJ-QL for pgsql-pkg-yum@lists.postgresql.org; Thu, 28 Sep 2023 18:10:02 +0000 Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-59f7cc71e2eso107932757b3.0 for ; Thu, 28 Sep 2023 11:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=noaa.gov; s=google; t=1695924600; x=1696529400; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uE/59LMG0o/RXAWNJaBe86TipO0Otfojbawx3BOJQSE=; b=SlZtqknmHUKLy8+lftIq/zxFghMD8Aeklf5r0z6g4fLfenFKAaOhfx+QZyf6eEvZXA Fy0O7yM9Rv59p+CCRf3AMVCQ1zRPusigVuCdzG9EOpTjeyglHHeuYyaXGjyIF6ZKAdPB qbLWUzQhD3v6vI+eCSdey9dfzcPB0Au4KecQsEG1WYLam8IsdsoS+J1S0+QukM3DRPpg Ea47ggFBspW1gCgUtEgMpGwm1b9nM5ZPml3RiimX77n/aXB92AzknS6czM6WvK43/u7p QJ41cTqsYuz1uSlnnz7rIk1TM/hDRHXRY0+RYCrrZTPd9zF2wnQPvXYJys4Y2JdQwtX9 Zf+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695924600; x=1696529400; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uE/59LMG0o/RXAWNJaBe86TipO0Otfojbawx3BOJQSE=; b=ga0y8WaUM1bi5HwCIO/1H/WWvw3ttB/PvXelcniDq8yfmpKMvI0bGLVsb7zwW1WWbJ rMBdPWS31PlmxhqgcCyAyjS6Vp/f8Bia3/KD8/yxZhiO/uy6yMAKarHjXDZn/DMsLjOF 1epDJPkmkP4a52VGf4tm807qPrEuIBtFKiIMT25tJzg9M6+HWCzh6IpuTivk9EpJeMxp oEaXl9Wa6ZfYLNaYo/AxBm34IZrjcbpQGlD8x3tFU5l15ls8ylA/hN+S16ywC8rY8UgW CfsqJJ5uzLGUwg98B39Am1CeVjQbbVCA8Vrfbc9za+i1zwTLjNoys8+isVBXQD705E76 eS7w== X-Gm-Message-State: AOJu0Yzkvf4xxbsMUEBFCDJYFglKeZ6Skr28TLDQB7BTRXR7brNgAcoj Gn8j+vJ2wMBy+vg+bzhnzG5x/AYI7SpFzjsz1R6wAZ88aFwzogZiVWnEaw== X-Google-Smtp-Source: AGHT+IGpG4/2Bpe4Nqk5erQI7XoeM2HIff9ZLVYrEgZUAVENK2WAR/v6PIaN7I5n1QsoVQSGj9ZqyjNTgrwulaj7kfU= X-Received: by 2002:a0d:d94f:0:b0:56d:d58:82b7 with SMTP id b76-20020a0dd94f000000b0056d0d5882b7mr2019287ywe.23.1695924599866; Thu, 28 Sep 2023 11:09:59 -0700 (PDT) MIME-Version: 1.0 References: <9d891a1580ee6ed9feae568f842a3998efb53191.camel@cybertec.at> In-Reply-To: From: Timothy Kempisty - NOAA Federal Date: Thu, 28 Sep 2023 14:09:48 -0400 Message-ID: Subject: Re: Dependencies for PostGIS 3.4 for PG v16 on Fedora 38 seem wrong To: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= Cc: Laurenz Albe , pgsql-pkg-yum@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000576e2006066f378b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000576e2006066f378b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am having similar problems on the RHEL8 repo. Everything is broken. Multiple geos dependencies means the postgis_raster extension is broken. If I try to use the latest postgis34 packages, then it only brings in geos312. That part works, but the problem becomes gdal36. gdal36-python-tools brings in EPEL's python3-gdal instead of PGDG gdal36-python3 from pgdg-common. The python module "osgeo_utils" only comes with the PGDG gdal36-python3 package. That means gdal36_python-tools / gdal_calc.py is dead. I can't install gdal36-python3 on top of python3-gdal to get the osgeo_utils, because the packages conflict. I have a big infrastructure as code project that relies on the PGDG RHEL8 repo. GDAL, postgis_raster, gdal-python-tools.... it worked earlier this month, but it's now dead in the water. Do we have a timeline here? Am I stuck retooling this to build geos, gdal, and postgis from source? -Tim On Thu, Sep 28, 2023 at 1:48=E2=80=AFPM Devrim G=C3=BCnd=C3=BCz wrote: > > Hi Laurenz, > > That stack is completely broken, and I'm trying my best before v16 is > out. > > Sorry about the inconvenience. > > Regards, Devrim > > On Wed, 2023-08-30 at 09:13 +0200, Laurenz Albe wrote: > > The dependencies look like this on my machine: > > > > > rpm -q --requires postgis34_16 | grep geos > > geos311 >=3D 3.11.2 > > libgeos_c.so.1()(64bit) > > > > > rpm -q --requires postgis34_16 | grep gdal > > gdal36-libs >=3D 3.6.3 > > libgdal.so.32()(64bit) > > > > > rpm -q --requires gdal36-libs | grep geos > > geos312 > > libgeos_c.so.1()(64bit) > > > > So postgis34_16 depends on both GEOS 3.11 and GEOS 3.12. > > One dependency is direct, the other is via GDAL. > > > > Yours, > > Laurenz Albe > > > > > > -- > Devrim G=C3=BCnd=C3=BCz > Open Source Solution Architect, PostgreSQL Major Contributor > Twitter: @DevrimGunduz , @DevrimGunduzTR > > > > --000000000000576e2006066f378b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am having similar problems on the RHEL8 repo.=C2=A0 Ever= ything is broken.=C2=A0 Multiple geos dependencies means the postgis_raster= extension is broken.=C2=A0 If I try to use the latest postgis34 packages, = then it only brings in geos312.=C2=A0 That part works, but the problem beco= mes gdal36.=C2=A0 =C2=A0gdal36-python-tools brings in=C2=A0 EPEL's pyth= on3-gdal=C2=A0instead of PGDG gdal36-python3 from pgdg-common.

The p= ython module "osgeo_utils" only comes with the PGDG gdal36-python= 3 package.=C2=A0 That means gdal36_python-tools / gdal_calc.py is dead.=C2= =A0 I can't install gdal36-python3 on top of python3-gdal to get the os= geo_utils, because the packages conflict.

I have a big infrastructur= e as code=C2=A0project that relies on the PGDG RHEL8 repo.=C2=A0 GDAL, post= gis_raster, gdal-python-tools....=C2=A0 =C2=A0it worked earlier this month,= but it's now dead in the water.=C2=A0 Do we have a timeline here?=C2= =A0 Am I stuck retooling this to build geos, gdal, and postgis from source?=

-Tim


On Thu, Sep 28, 2023 at 1:48= =E2=80=AFPM Devrim G=C3=BCnd=C3=BCz <devrim@gunduz.org> wrote:

Hi Laurenz,

That stack is completely broken, and I'm trying my best before v16 is out.

Sorry about the inconvenience.

Regards, Devrim

On Wed, 2023-08-30 at 09:13 +0200, Laurenz Albe wrote:
> The dependencies look like this on my machine:
>
> > rpm -q --requires postgis34_16 | grep geos
> geos311 >=3D 3.11.2
> libgeos_c.so.1()(64bit)
>
> > rpm -q --requires postgis34_16 | grep gdal
> gdal36-libs >=3D 3.6.3
> libgdal.so.32()(64bit)
>
> > rpm -q --requires gdal36-libs | grep geos
> geos312
> libgeos_c.so.1()(64bit)
>
> So postgis34_16 depends on both GEOS 3.11 and GEOS 3.12.
> One dependency is direct, the other is via GDAL.
>
> Yours,
> Laurenz Albe
>
>

--
Devrim G=C3=BCnd=C3=BCz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR



--000000000000576e2006066f378b--