On Mon, Oct 5, 2020 at 7:10 PM Antal Nemeš Antal.Nemes@hycu.com wrote:
-----Original Message----- From: CentOS-devel centos-devel-bounces@centos.org On Behalf Of Johnny Hughes Sent: Monday, 5 October 2020 16:53 To: centos-devel@centos.org Subject: Re: [CentOS-devel] Module version differences between RHEL8 and Centos8?
On 10/4/20 4:54 PM, Antal Nemeš wrote:
Is there any way to correlate modular package versions in RHEL8.x with
ones from Centos8.x in any way, no matter how difficult?
For example, looking at package list for
https://access.redhat.com/errata/RHSA-2020:3714:
- RedHat lists httpd-2.4.37-21.module+el8.2.0+5008+cca404a3.x86_64.rpm
- in CentOS this (probably?) matches
httpd-0:2.4.37-21.module_el8.2.0+494+1df74eae.x86_64
AFAIK, the non-modular packages shared the same NEVRA between RHEL
and Centos (not sure if there were exceptions, though).
Modules are built by a new component called MBS (Module Build System) .. it works in conjunction with KOJI to do bulids.
Because of MBS, exact module names are not possible between RHEL and CentOS. This is because 2 things in MBS are generated at build time. One is an index number .. one is a commit hash from git.
Since git.centos.org is a closed system and it's hashes will be different than the internal RHEL git repo .. the hashes will never match for commits.
Also, since the CentOS MBS is a sperate system frmo the RHEL Build System .. the index number for build will also never be the same.
Therefore, modules will never patch with exact names.
Thanks, that explains a lot
Doesn't the import of sources into git.centos.org represent state from internal RHEL repos that produced released RHEL packages?
It represents the SRPMs that are in the released RHEL packages.
Does this import contain any kind of hash reference or any kind of identifier from RHEL repo, such that it could be used to link RHEL released modules with Centos?
It does not, because the source is pushed from SRPMs, not the internal RHEL git repositories.
josh