Hide Forgot
Description of problem: rpm verify screams about changed config right after installation because rpm scriptlet. this is quite strange behaviour (according to me). # rpm -q --scripts redhat-support-plugin-rhev | tail -n2 #Add version to config file printf "\nversion=com.redhat.gss-redhat-support-plugin-rhev-3.3.0-0.scratch" >> /etc/ovirt-engine/redhatsupportplugin.conf # rpm -q redhat-support-plugin-rhev redhat-support-plugin-rhev-3.3.0-7.el6ev.noarch # rpm -qV redhat-support-plugin-rhev S.5....T. c /etc/ovirt-engine/redhatsupportplugin.conf Version-Release number of selected component (if applicable): is17 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: rpm verify issue Expected results: default is default and verify should be OK Additional info: I suppose you now the version while you are building the rpm, thus you can put the version (if it is needed anyway) into the config during build
OK, redhat-support-plugin-rhev-3.3.0-8.el6ev.noarch.
This bug is currently attached to errata RHBA-2013:15513. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Hi does this need doc text? If so what was the fix? Thanks
This fix should not need doc text.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0082.html