Convince the developers to use versioned symbols when they break the API/ABI.
This is the 21st Century, and we have solutions for this. It's not rocket surgery.
</top post>
That's actually not a problem most of the time. Some upstreams even unnecessarily bump their soversion. But maintaining two (or potentially more) versions of a library does create significant extra work for the packager. One example is the Coin package, currently Coin2/Coin3/Coin4 with all the alternatives gunk.