Hi Is there an statement in Debian Policy that explicitly requires higher version of a shared library package to be backwards-binary-compatible with previous versions of the same package?
I mean, is a situation when after library package upgrade local binaries stops working because of missing symbols, by definition an RC bug against library package? Or is depends on particular situation? Nikita P.S. Please CC replies to my e-mail address.
signature.asc
Description: This is a digitally signed message part.
