Dirk Eddelbuettel wrote: > On 18 November 2009 at 18:55, Robert Edmonds wrote: > | since the changes from 2.1.0 to 2.2.0 have demonstrably broken ABI > | compatibility, the SONAME really should be bumped, regardless of NEW > | delays, etc. because it is the correct thing to do, rather than breaking > | unrelated software. ideally it should be coordinated with upstream so > | that we don't break binary compatibility with other linux distributions > | (to the extent that this is possible with the C++ ABI, which i am not > | especially familiar with). > > That is correct if you narrowly play by the book, but in the grand scheme of > things it is still somewhat silly that among 8k or 9k source packages we do > these dances for packages whose 'dependency graph' has one edge and one > further package.
narrowness doesn't enter into it; package renames due to SONAME bumps
are required by policy.
Debian Policy Manual
Chapter 8 - Shared libraries
8.1 Run-time shared libraries
The run-time shared library needs to be placed in a package whose name
changes whenever the shared object version changes.
in this case it was an upstream bug that the SONAME was not increased,
and three packages (mumble, mumble-server, protobuf-c-compiler), not
one, were affected.
--
Robert Edmonds
edmo...@debian.org
signature.asc
Description: Digital signature
