Red Hat Bugzilla – Bug 472151
rpm verify fails after a fresh install
Last modified: 2009-10-26 18:03:14 EDT
Created attachment 323985 [details]
Proposed patch adapted from upstream (only the line numbers changed).
Description of problem:
Running "rpm -Va" on a freshly-installed x86_64 system reports
thousands of files with mtimes that differ from the original
package. This pretty much makes rpm verification useless.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install new x86_64 system.
2. run "rpm -Va"
Many files differ from the ones in the RPM package. Most of them
differ only in their mtime and are the ones that belong to
"rpm -Va" should list only the files that have actually changed
This is one of the complaints put forth in Bug 426672. This has also
been addressed in upstream rpm:
Backporting the fix is easy, devel ack for 5.4.
*** Bug 508855 has been marked as a duplicate of this bug. ***
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
adding QAkeyword RHTSinProgress:
* rhts test created:
-- test fail due to bug 506922 : there are many different /usr/shared docs files, that's why fails
expected differs + md5 docs differs
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.