public inbox for [email protected]
help / color / mirror / Atom feedFrom: Devrim Gündüz <[email protected]>
To: Eduar Flow <[email protected]>
To: M, Anbazhagan <[email protected]>
Cc: [email protected]
Subject: Re: Clarification on Naming convention of the new recent packages #162
Date: Tue, 10 Mar 2026 11:38:26 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALR9rdT2_cQ2W5ECt0yn8OeetX+KV8T8chDwNcsHWGRbkddLqg@mail.gmail.com>
References: <MN2PR06MB6637E038DE9087619FBAF82CFF7DA@MN2PR06MB6637.namprd06.prod.outlook.com>
<[email protected]>
<MN2PR06MB663745EF334D025FEFBACC32FF79A@MN2PR06MB6637.namprd06.prod.outlook.com>
<CALR9rdT2_cQ2W5ECt0yn8OeetX+KV8T8chDwNcsHWGRbkddLqg@mail.gmail.com>
Hi,
On Mon, 2026-03-09 at 10:44 -0600, Eduar Flow wrote:
> The PGDG RPMs for RHEL 8 are typically built against the most recent
> minor release available (currently 8.10). Because Red Hat Enterprise
> Linux maintains ABI compatibility across RHEL 8 minor versions,
> packages built on 8.10 remain compatible with earlier minor releases
> such as 8.9, 8.8, etc.
>
> For that reason, the package naming may include the ".rhel8.10" suffix
> even when the RPM is located in repositories corresponding to earlier
> minor versions like "rhel-8.9-x86_64".
>
> In short, the suffix reflects the build environment rather than a
> strict requirement for that exact minor release.
If this is an AI response, it is not funny and it is incorrect. If this
is not AI response, it is incorrect.
Per:
https://access.redhat.com/articles/rhel8-abi-compatibility
https://access.redhat.com/articles/rhel9-abi-compatibility
https://access.redhat.com/articles/rhel10-abi-compatibility
"During the life cycle of a major release, Red Hat makes commercially
reasonable efforts to maintain the binary compatibility of the runtime
environment across all minor releases and errata advisories. If
necessary, Red Hat may make exceptions to this compatibility goal for
critical impact security or other significant issues."
Regards,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
BlueSky: @devrim.gunduz.org , @gunduz.org
Attachments:
[application/pgp-signature] signature.asc (858B, 2-signature.asc)
download
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Clarification on Naming convention of the new recent packages #162
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox