<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sun, Oct 6, 2019, at 21:05, Ladar Levison via CentOS-devel wrote:<br></div><blockquote type="cite" id="qt"><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">Can someone explain
what's going on with the kernel? The kernel-4.18.0-80.7.1
package is the latest available via the repos, despite
kernel-4.18.0-80.11.2 having been compiled 16 days ago.
(<a href="https://koji.mbox.centos.org/koji/buildinfo?buildID=4562" class="qt-moz-txt-link-freetext">https://koji.mbox.centos.org/koji/buildinfo?buildID=4562</a>) The
koji downloads appear to still be blocked.</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">The kernel-4.18.0-144
kernel used to be available via the Stream-BaseOS repo, but it
no longer appears to be showing up. The package is still
available for download, but it doesn't appear via dnf (although
it has previously). I suspect the package was removed from the
repo metadata, but the rpm file remains.
(<a href="http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/kernel-4.18.0-144.el8.x86_64.rpm" class="qt-moz-txt-link-freetext">http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/kernel-4.18.0-144.el8.x86_64.rpm</a>) </span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">To make things even
more confusing, the kernel-4.18.0-80.7.2 package was compiled a
few days ago. And like the newer kernel-4.18.0-80.11.2, appears
to have never been pushed to the repos.
(<a href="https://koji.mbox.centos.org/koji/buildinfo?buildID=4618" class="qt-moz-txt-link-freetext">https://koji.mbox.centos.org/koji/buildinfo?buildID=4618</a>)</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">So my question is why
is kernel-4.18.0-80.11.2 available? Why was the older </span><span style="font-family:Helvetica, Arial, sans-serif" class="font">kernel-4.18.0-80.7.2 built,
and then never released? Is there an issue with these packages
in need of fixing, or it simply a bug in the release/repo
process?</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">The following issues
were addressed by these newer kernel packages:</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">RHSA-2019:2411 /
CVE-2019-1125 & CVE-2019-13272</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">RHSA-2019:2703 /
CVE-2019-3846 & CVE-2019-3887 & CVE-2019-9500 &
CVE-2019-9503 & CVE-2019-11487 & CVE-2019-12817 &
CVE-2018-19824</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">RHSA-2019:2827 /
CVE-2019-14835</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">I haven't looked into
the details, but at first glance the issues seem rather
important.</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font">L~</span><br></p><p><span style="font-family:Helvetica, Arial, sans-serif" class="font"></span><br></p><div>_______________________________________________<br></div><div>CentOS-devel mailing list<br></div><div>CentOS-devel@centos.org<br></div><div>https://lists.centos.org/mailman/listinfo/centos-devel<br></div><div><br></div></blockquote><div><br></div><div><br></div><div>We have a large batch of updates that we were hoping to get out together, but we're still bootstrapping dependencies on a few packages. <br></div><div><br></div><div>I can't give an estimate of when this next batch will go out, but if our blockers continue too much longer we'll attempt to split the batch and release what's ready.<br></div><div><br></div><div>--Brian<br></div></body></html>