Re: libcommoncpp2 library transition
* Mark Purcell [Wed, 18 Mar 2009 21:20:54 +1100]:
> Looks like libcommoncpp2 transition is complete and just needs your
Unfortunately, it is not that simple. It is true that all packages have
been rebuilt in unstable. But, to begin with, libcommoncpp2 is tied to
the libosip2 transition via bayonne. Which isn’t too bad, really because
libosip2 is almost ready itself.
However, libosip2 is tied to ffmpeg and libraw1394 via linphone, and
that isn’t as good. I was planning to keep the old libosip2-3deb in
testing to untie them, but (again) it is not that simple: both bayonne
and linphone depend on libexosip2-4 and libosip2. If I leave linphone
unmigrated and bayonne migrates, each will link to the appropriate
libosip2; but they will link against the same version of libexosip2-4,
which will link against libosip2-4, and which will mean two versions of
libosip2 and libcommoncpp2 will be loaded into the process space of
Anyway, I don’t want to bore you with the details. I wanted to see if
the version of linphone in testing rebuilds fine in testing against the
new libcommoncpp2 and the new libosip2. If that’s the case, we may push
it through soon, and do Bin-NMUs for linphone in testing.
Mark, could you try if that’s the case?
- Are you sure we're good?
-- Rory and Lorelai