[CentOS-devel] kernel-4.18.0-193.14.2.el8_2 in git.centos.org

Johnny Hughes

johnny at centos.org
Mon Aug 3 15:19:20 UTC 2020

On 8/3/20 9:43 AM, Antal Nemeš wrote:
>> -----Original Message-----
>> From: CentOS-devel <centos-devel-bounces at centos.org> On Behalf Of Brian
>> Stinson
>> Sent: Monday, 3 August 2020 16:14
>>> I believe 14.3 is exactly the same as 14.2 except that RH needed to
>>> adjust the signing order of their certificates and since those are RH
>>> specific, 14.2 == 14.3 for the intents and purposes of non-RHEL builds.
>>> Trevor
>> This is the correct answer. The difference between 14.2 and 14.3 is only
>> applicable to RHEL, and is not a change in the underlying content. The CentOS
>> kernels were dual-signed in the right order for us in 14.2
>> --Brian
> Great, thanks for confirmation. This throws a gigantic monkey wrench in my attempts 
> at automating src.rpm generation from git.centos.org, so I hope this was an exceptional occurrence?

Yes .. one could say that an embargoed, 'named' sescureboot/kernel fix
that requires a signature from Microsoft before release AND requires
hiding embargoed content (which CentOS is not set up to do ..we build
everythign in the open) .. is VERY MUCH an exceptional occurrence.

Then throw in the fact the both RHEL and CentOS installs could no longer
BOOT .. I think you are it the most unbelievable and most complicated
build we have ever done in as the CentOS Project.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20200803/128708f2/attachment-0002.sig>

More information about the CentOS-devel mailing list