Description of problem:
TPS RHNQA in the errata tool found an issue with our 5.11 cpuspeed package. Here is what I think happened:
We cut a new cpuspeed package for 5.11 to fix bz 887256 (1.2.1-11.el5). Some time later we got a request to build a z-stream package with the same fix in it (1.2.1-11.el5_10, bz 1078211) and we released it. Systems with cpuspeed installed now can only update to version 1.2.1-11.el5_10 since rpm considers that package to be newer than 1.2.1-11.el5.
It appears that we need to re-spin cpuspeed to bump up the release number so it will appear to be newer than the 5.10.z version. No code changes should be needed.
Version-Release number of selected component (if applicable):
cpuspeed-1.2.1-11.el5_10 & cpuspeed-1.2.1-11.el5
Steps to Reproduce:
1. Try an yum update to 5.11 cpuspeed with the 5.10.z version installed.
only cpuspeed-1.2.1-11.el5_10 is available
5.11 version of cpuspeed needs a higher release number so it appears newer to rpm/yum
I think this is a rather common situation. Is the update even necessary? The contents of the packages are identical and any hypothetical future updates would automatically update from 1.2.1-11.el5_10 to 1.2.1-12.el5+.
This was resolved by dropping the 5.11 errata.