<div dir="auto">I must point out that the kernel source must of been jumped at some "consolidated", time in the past from an agreement between groups. Which all have a code which they can see or identify and continue to receive money from corporate interests by seek and destroy methods for rival competition. Most likely a gps malfunction in a computer system which had the kernel caught without the tampered ID put in for queue to make the next one you compile also bugged.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 1, 2023, 1:25 AM John Pilkington <<a href="mailto:johnpilk222@gmail.com">johnpilk222@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 31/10/2023 15:32, Akemi Yagi wrote:<br>
> On Tue, Oct 31, 2023 at 4:00 AM John Pilkington <<a href="mailto:johnpilk222@gmail.com" target="_blank" rel="noreferrer">johnpilk222@gmail.com</a>> wrote:<br>
>><br>
>> On 30/10/2023 20:38, Akemi Yagi wrote:<br>
>>> Announcing the release of the kernel-ml-6.0.0-1.el7.elrepo package set<br>
>>> into the EL7 elrepo-testing repository:<br>
>>><br>
>><br>
>> Hi Akemi: The previous release, which I'm running, was<br>
>><br>
>> john@HP_Box ~]$ uname -r<br>
>> 6.5.9-1.el7.elrepo.x86_64<br>
> <br>
> D'oh. It's supposed to be 6.6.0-1. I'll resend the announcements.<br>
> <br>
> Akemi<br>
<br>
Thanks, but I think it wasn't just the announcement. yum sees only <br>
6.5.7, 6.5.8 and 6.5.9<br>
<br>
No panic here, but just FYI.<br>
<br>
John<br>
<br>
_______________________________________________<br>
elrepo mailing list<br>
<a href="mailto:elrepo@lists.elrepo.org" target="_blank" rel="noreferrer">elrepo@lists.elrepo.org</a><br>
<a href="http://lists.elrepo.org/mailman/listinfo/elrepo" rel="noreferrer noreferrer" target="_blank">http://lists.elrepo.org/mailman/listinfo/elrepo</a><br>
</blockquote></div>