Description of problem: rpm-database has weird state for multilib packages. It shows files not existing there while even succeeding their verification (-V). Version-Release number of selected component (if applicable): rpm-4.4.2-15.2 How reproducible: Always. Steps to Reproduce: 1. rpm -qlv dbus.x86_64 dbus.i386|grep '/bin/dbus-daemon$' 2. rpm -V dbus.x86_64 dbus.i386|grep '/bin/dbus-daemon$' Actual results: 1. -rwxr-xr-x 1 root root 639104 May 5 19:40 /bin/dbus-daemon -rwxr-xr-x 1 root root 687816 May 5 19:41 /bin/dbus-daemon 2. [nothing] Expected results: 1. -rwxr-xr-x 1 root root 687816 May 5 19:41 /bin/dbus-daemon 2. [nothing] Or some other indication that the .i386 file instance does not exist there. Additional info: I have seen even -V failing the verification but I cannot reproduce it now. The -V step was correct this way but the whole user perception is also wrong. "dbus" is only a multilib package sample here.
Files have state associated, display a file's state by doing rpm -qs dbus.i386 | grep daemon You should see the state "wrong color", meaning that rpm chose to install the ELF64, not the ELF32, executable. Uninstalled files are skipped with --verify. NOTABUG
Oops, I missed this option, I even searched for such one, thanks.