Description of problem: After initial installation rpm is happy but once prelink is run rpm always flags /bin/traceroute6 as faulty This false positive is very annoying when looking for FS damage Version-Release number of selected component (if applicable): traceroute-1.0.4-1.x86_64.rpm
I'm not sure what's the problem here. /bin/traceroute6 is now symlink, so prelink should only run on /bin/traceroute ..
Well you know I had a FS problem, so I did a -Va and forced reinstall of all packages rpm reported a problem on After the reinstall rpm -V traceroute didn't report any problem Five minutes later (after running prelink cron manually, maybe the system did something else too) traceroute was once again marker as faulty SM5.....C /bin/traceroute6
Ok, this doesn't work for me, so it seems that there's sth else broken on your system. I tried forced reinstall and let prelink go through all binaries and it's still fine. If you find a clear steps to reproduce this issue, be free to reopen this bug.
Well, I reproduce it all the time like this : [root@rousalka tmp]# rpm -V traceroute SM5.....C /bin/traceroute6 [root@rousalka tmp]# rpm -K traceroute-1.0.4-1.x86_64.rpm traceroute-1.0.4-1.x86_64.rpm: (sha1) dsa sha1 md5 gpg OK [root@rousalka tmp]# rpm -Uvh --force traceroute-1.0.4-1.x86_64.rpm Préparation... ########################################### [100%] 1:traceroute ########################################### [100%] [root@rousalka tmp]# rpm -V traceroute [root@rousalka tmp]# /etc/cron.daily/prelink [root@rousalka tmp]# rpm -V traceroute SM5.....C /bin/traceroute6 (everything is already prelinked so the prelink phase is so fast I doubt anything else is causing the problem)
Than it's maybe a rpm bug, cos it shouldn't verify md5 sums on symlinks. Can you verify the checksums? Get the file list checksum rpm -q --qf '[%{FILEMD5S} %{FILENAMES}\n]' traceroute and compare it to /usr/sbin/prelink -y --md5 /bin/traceroute /usr/sbin/prelink -y --md5 /bin/traceroute6 (they should be same, as traceroute6->traceroute)
The checksums seem fine but rpm still complains : [root@rousalka tmp]# /usr/sbin/prelink -y --md5 /bin/traceroute 01a807a837a29fce2f8af4ec3ee68d35 /bin/traceroute [root@rousalka tmp]# /usr/sbin/prelink -y --md5 /bin/traceroute6 01a807a837a29fce2f8af4ec3ee68d35 /bin/traceroute6 [root@rousalka tmp]# rpm -q --qf '[%{FILEMD5S} %{FILENAMES}\n]' traceroute 01a807a837a29fce2f8af4ec3ee68d35 /bin/traceroute /bin/traceroute6 /usr/share/doc/traceroute-1.0.4 4c4203caac58013115c9ca4b85f296ae /usr/share/doc/traceroute-1.0.4/COPYING.GPL 453661e9a63c20d2242274ef5d6b8c4b /usr/share/doc/traceroute-1.0.4/ChangeLog d226e2ead81bd4f28a91b863cfed59ff /usr/share/doc/traceroute-1.0.4/README a6f7b3e10ea747be9a3e0a032076d9e6 /usr/share/man/man8/traceroute.8.gz /usr/share/man/man8/traceroute6.8.gz [root@rousalka tmp]# rpm -V traceroute SM5.....C /bin/traceroute6
Reassignig to rpm for some hints ..
Problem non-reproducible on CentOS 4.2: [root@localhost ~]# rpm -V traceroute [root@localhost ~]# /etc/cron.daily/prelink [root@localhost ~]# rpm -V traceroute [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.9-22.ELsmp #1 SMP Sat Oct 8 21:32:36 BST 2005 x86_64 x86_64 x86_64 GNU/Linux Hmmm, the 'C' means that SElinux file contexts on the file system don't match whatever policy is currently installed. Try using restorecon on /usr/sbin/traceroute6 (or boot with selinux disabled). Does that change the behavior? Ifr so, I think you kinow where to shove this bug.
rpm-4.4.4-1 built on vanilla CentOS 4.2.
No response, so back to traceroute.