From: "Nicolas Ross" <rossnick-lists@cybercat.net>
Subject: Re: Can't update RPM package to latest version
To: "pgsql-admin@lists.postgresql.org"
 <pgsql-admin@lists.postgresql.org>
Date: Thu, 20 Nov 2025 11:35:04 -0500
Message-ID: <web-285452913@mail.cybercat.ca>
In-Reply-To: 
 <YT2P288MB01728DF6694056B1FA5A20BDB9D4A@YT2P288MB0172.CANP288.PROD.OUTLOOK.COM>
References: <web-285449613@mail.cybercat.ca>
 <YT2P288MB01728DF6694056B1FA5A20BDB9D4A@YT2P288MB0172.CANP288.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/web-285452913%40mail.cybercat.ca>
Precedence: bulk

openssl-libs is at 3.2.2.6.el9_5.1 and has no update. I
suppose that it's a downstream from RH problem ?

On Thu, 20 Nov 2025 16:28:28 +0000
 Evan Rempel <erempel@uvic.ca> wrote:
> The latest release from RedHat, that came out this month
> is
> 
> $ rpm -q --whatprovides
> 'libcrypto.so.3(OPENSSL_3.4.0)(64bit)'
> Openssl-libs-3.5.1-3.el9.x86_64
> 
> At our site we freeze deployment of packages at the
> beginning of the month so that our prod hosts get the
> same packages that were updated/deployed in our dev
> environments.
> 
> This package, frozen from the beginning of the month is
> only
> openssl-libs-3.2.2-6.el9_5.1.x86_64
> 
> which does not satisfy this requirement. On a system that
> has the actual latest packages from RedHat this package
> has been updated to
> openssl-libs-3.5.1-3.el9.x86_64
> 
> % rpm -q --whatprovides
> 'libcrypto.so.3(OPENSSL_3.4.0)(64bit)'
> openssl-libs-3.5.1-3.el9.x86_64
> 
> If you update to the latest packages on your host, this
> requirement will be satisfied.
> 
> --
> Evan