Description of problem: When building new packages from time to time rpmbuild seems to create packages which depend both on "old" and "new" versions of shared libs but with that package providing only "new" libraries. Obviously it is impossible to install such packages in a clean way. For examples see bugs #150155 and #150623. It appears that "automatic dependency resolution" checks and uses both currently installed libraries and newly build ones too. I am not sure if this is a coincidence or some other differences in a build process but so far I did not see that problem with x86_64 packages but only with their i386 equivalents. If "rawhide" packages are really build by some other process then what is responsible for that trouble?
This is no rpm problem. Open bugs against specific packages if there are linkage problems with both old and new libraries.