Sharpe, Sam J wrote:
On Thu, 2008-02-14 at 08:49 -0600, Daryl Herzmann wrote:
I was puzzled to see the most recent kernel errata come out with a version number of "2.6.18-53.1.13" compared with the last kernel of "...6", that's 7 bumps for fixing 1 security issue?

That refers to the build of the RPM, not the version of the kernel.
2.6.18 is the Kernel version, 53.1.13 is the RPM version number.

The kernel RPM version number usually always matches Red Hat's internal kernel version number.

The 53.1.13 version includes all errata from 53.1.6 -> 53.1.13 as reflected in the change log:

https://rhn.redhat.com/network/software/packages/change_log.pxt?pid=432821

Is it typical to see a critical kernel security fix that includes additional patches? I appreciate that Red Hat had to release this fix quickly, but still you have to wonder why Red Hat didn't just release the new kernel with error 432252 as the only fix. How do they decide when other changes are sufficiently safe to include along with time-critical security fixes? Or was it just easier to release it with the additional patches than to apply the fix to 53.1.6? It would be interesting to hear the thought process.



When I build an RPM, I change the version every time I make an update to
the RPM, whether it fixes an issue or it fixes a fix to an issue.

Lets say I apply a patch, so I bump the RPM version up. I then find out
that the patched binary didn't work properly, so I redo it (new
version). I then find out that fixing this broke some other thing, so I
correct that and rebuild (new version number). I then find out I forgot
to update the changelog in the .spec file, so I update that and rebuild
(new version number).

I can quite easily believe that including one patch requires multiple
RPM rebuilds and therefore a huge number of version changes in the
RPM... which explains why it's 2.6.18-53.1.13 rather than 2.6.18-11 (I'm
making up the 11 versions, I think there's been loads more kernel RPM
releases in RHEL4.)

--
Sam

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

John D

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to