When x86_64 executables replace i386 executables, the
i386 executable is marked "replaced" rather than "normal".
The file state can be displayed with "rpm -qs pkg" (which is essentially
what you are asking for, a way to detect files that are not installed
and so the package may not function).
The "missing" from --verify is the specific condition of a "normal" file
that is not present on the file system.
There are other not installed conditions, not just "replaced", that cannot
be bundled into a --verify "missing" category for an all purpose spewage.
The real flaw is that rpm should undertake restoring the i386 executables
when removing a x86_64 package. But that gonna happen soon (if ever).
When x86_64 executables replace i386 executables, the
i386 executable is marked "replaced" rather than "normal".
The file state can be displayed with "rpm -qs pkg" (which is essentially
what you are asking for, a way to detect files that are not installed
and so the package may not function).
The "missing" from --verify is the specific condition of a "normal" file
that is not present on the file system.
There are other not installed conditions, not just "replaced", that cannot
be bundled into a --verify "missing" category for an all purpose spewage.
The real flaw is that rpm should undertake restoring the i386 executables
when removing a x86_64 package. But that gonna happen soon (if ever).