[elrepo] kmod-ecryptfs.x86_64 on Centos Stream fails

[Trevor Hemsley]

On 31/01/2021 14:14, lejeczek via elrepo wrote:
>
>
> On 31/01/2021 13:44, Trevor Hemsley wrote:
> > On 31/01/2021 10:38, lejeczek via elrepo wrote:
> > > Does anybody else get this and if yes then should it go to
> > > bugzilla?
> >
> > ELRepo do not support Stream since it uses a different,
> > non-KABI stable,
> > kernel series to RHEL. This is something that's come up
> > several times in
> > the mailing list etc threads on what Red Hat are doing
> > with CentOS Linux 8.
> >
> > Trevor
> >
> And what is the actual problem? Surely it's not one of
> technical nature.
> Increasingly more of us will be ridding "Stream" as months
> go by.

The problem is that RH make changes to the "stable" KABI between point 
releases - which is normal practice and has been for years - and for 
RHEL and CentOS Linux, you only get to see those changes take place 
once, at point release time. That's why ELRepo end up having to rebuild 
a bunch of kmods at each point release to allow them to continue to work.

With Stream, RH are now making those same KABI changes but the kernels 
in which those changes are made are released to Stream immediately so 
the KABI change happens almost immediately after the release of the 
current RHEL point release. At that time Stream and RHEL have different 
"stable" KABI's and you can no longer use the current RHEL point release 
kmods on the newer Stream kernel (Stream already has the kernel version 
from the _next_ point release that won't be released for up to 6 months).

To give a concrete example, RHEL 8.3 and CentOS Linux 8.3 are using 
kernel-4.18.0-240* kernels and the KABI works for all 4.18.0-240* series 
kernels. Stream got a 4.18.0-269* kernel on 2021-01-12 20:36and before 
that it had a 4.18.0-267 kernel and that -267 kernel came out about 2 
days after the release of CentOS Linux 8.3 so Stream and CL8 shared a 
common KABI for approximately 2 days.

This is not something that ELRepo can fix since to do so for Stream now 
means that they might need to rebuild all 50 kmods every time a new 
Stream kernel comes out and until they do, all current users who have 
upgraded their kernel to $latest will have broken kmod packages that 
will not function. The effect of that is that ELRepo would go from a 
part-time "let me just do an hour or two at the weekend" maintenance 
schedule to a "I have a new full time job".

Trevor

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20210131/25b33c12/attachment-0001.html>