I just got burned by this pretty bad. I don't know if preserve_old_lib_notify() is exactly the place, or if there are several, but it's an example at least. Turns out my gcc had linked against /usr/lib/libmpfr.so.1 for some reason (instead of /usr/lib64/libmpfr.so.1). So, being a good little sheep, after I upgraded mpfr, I did as I was told by this warning and ran: "revdep-rebuild --library '/usr/lib64/libmpfr.so.1'" and then deleted /usr/lib64/libmpfr.so.1. That made GCC, which hadn't been detected or rebuilt (somewhat understandably so, I only told it to look at lib64), not able to function. (Luckily for me, a soft link to the newer libmpfr.so.4 allowed gcc to function until I could rebuild gcc and get out of trouble.) So, I'd suggest, that everywhere this type of ewarn is output, it should automatically also suggest checking the non-64 version of the string as well. This will mean longer revdep-rebuild searches, but should keep people from near-bricking their install. An alternative would be to put the smarts in revdep-rebuild itself. This only applies to setups that use lib64, so x86 doesn't need any of this. Reproducible: Always
*** This bug has been marked as a duplicate of bug 357225 ***
