Comment 6 for bug 633691

(In reply to comment #3)
> One can already fiddle up the logic with --verify to filter the
> output to meet opinions of common perceptions and luser
> expectations. One can already do that in packaging, or with
> disablers from the CLI, and it wouldn't be more than 2-4 lines
> of code to also make --verify output configuration persistent.
>
> Detecting a replaced and then removed file is no harder than
> coupling a state transition back to "normal" when the package
> of the other arch is removed, thereby inverting the transition
> that occurred when one of the packages was installed.

This isn't quite enough: if a 32-bit executable is replaced and then the 64-bit one gets damaged, I want to see that when verifying the 32-bit package.