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

[Fabian Arrotin]

On 03/02/2021 10:48, lejeczek via elrepo wrote:

<snip>
>>
>> In addition to the detailed explanation by Trovor and also by wolfy,
>> you can refer to the ELRepo blog post:
>>
>> http://elrepoproject.blogspot.com/2021/01/elrepo-and-centos-stream.html <http://elrepoproject.blogspot.com/2021/01/elrepo-and-centos-stream.html>
>>
>>
>> Akemi
>>
> You guys sound really worried as if RH is about to spit a new kernel
> every other day - do you really think that?
> Are Elrepo's kernel a work-around solution for cases with kmods and
> similar?
> many thanks, L.
> 

Well, it can happen and that will happen (there are some cases).
So we can easily understand that Elrepo volunteers don't have the
time/resources to deal with unpredicted new kernel drop in Stream.

So the question is more about : what *us*, community users, want to do
about it ?
As the stream kernel is available, it can be that some people just try
to rebuild it (in parallel of what Elrepo infra is doing, aka against
released RHEL kernel), and that can be either through a proposed SIG at
the CentOS side (and so built through https://cbs.centos.org), or just
something easier, like COPR public build repo
(https://copr.fedorainfracloud.org/) ?

Then point people to these packages for Stream users, and (that's the
added value) point Elrepo to .patch through git repo about what *would*
be then needed in the next RHEL major.minor kernel rebase  ?

I think that it's a win/win situation ? Stream users have kmod, and
Elrepo can benefit from community users' research on potential issues
and fixes ?

It's just a thought at this stage, but probably something to think about ?

-- 
Fabian Arrotin
gpg key: 17F3B7A1 | twitter: @arrfab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20210203/3db69860/attachment.sig>