On Fri, Aug 22, 2014 at 11:13:40PM +0200, Meikel wrote:
By browsing those tripwire reports I found that there are files which did not change at all (i.e. the MD5 hash is the same as before) but the inode changed. I do not understand what yum did to the file that resulted in an inode change, especially I'm wondering how the inode can change although there was no modification on the file at all.
Do you have redhat-lsb installed? I bet that this is related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=867124