View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004689||CentOS-5||kvm||public||2010-12-27 12:52||2011-05-04 17:32|
|Summary||0004689: Missing KVM update|
|Description||Please publish the latest kmod-kvm update (kmod-kvm-83-164.el5_5.30), released by TUV on December 20: |
|Additional Information||SRPMs available at:|
|Tags||No tags attached.|
Although this is rated 'low', it is a security update nonetheless. So, better to get it published. Is someone available to do this job?
|Bump2. Changing the priority from high to urgent now. Karanbir, Tru, ... who else can do this update?|
Yet another KVM security update has been released today: kmod-kvm-83-224.el5
More details at: https://rhn.redhat.com/errata/RHSA-2011-0028.html
What's the policy in such cases? I don't suppose publishing this previous update can now be skipped?
It (kmod-kvm-83-224.el5) is part of EL5.6 released today, so will not be out until the release of CentOS 5.6.
The "latest" kvm update (for the current 5.5) has to be published.
|Indeed, my mistake... sorry :-(|
|I see no mistake. What you wrote was all correct. :-)|
|I'll look into this. We have a few updates from 5.5/ in the pending queue stuck behind a package with bad linking issues. And toracat is right, all pending updates from the previous release also need to be pushed.|
|It is nice of you to say I am right. But it will be much nicer if you can actually push those pending updates. :-)|
Now that CentOS 5.6 is out, this request is a history. This kvm security update was missed 'forever' despite the fact that the request was bumped more than once and the priority was elevated to 'high' then to 'urgent'.
Instead of seeing this as a negative record, I suggest taking this a 'good' example and analyzing the reason why the update did not materialize. That should lead to a better implementation of the procedure for publishing security updates (my hope).
|2010-12-27 12:52||milosb||New Issue|
|2011-01-05 15:56||toracat||Note Added: 0012283|
|2011-01-05 15:57||toracat||Priority||normal => high|
|2011-01-10 16:28||toracat||Note Added: 0012325|
|2011-01-10 16:28||toracat||Priority||high => urgent|
|2011-01-13 21:08||milosb||Note Added: 0012343|
|2011-01-13 21:19||toracat||Note Added: 0012344|
|2011-01-13 22:14||milosb||Note Added: 0012345|
|2011-01-13 22:18||toracat||Note Added: 0012346|
|2011-01-13 23:firstname.lastname@example.org||Note Added: 0012347|
|2011-02-09 17:40||toracat||Note Added: 0012419|
|2011-05-04 17:32||toracat||Note Added: 0012708|