Bug#402009: libcommoncpp2-dev library transition proposal (Fwd: Bug#402009: Multiple API-incompatible changes in Common C++ 1.5.3)

[Steve Langasek]

Hi Mark,

On Sat, Dec 09, 2006 at 10:24:48AM +0000, Mark Purcell wrote:
> On Saturday 09 December 2006 10:10, Mark Purcell wrote:
> > The alternative, which is better, is just to back out the library
> > transition.

> Or even better-better, just don't do the library transition at all.

> The current state of libcommoncpp2 (1.5.1) and rdepends in etch is stable and 
> supportable. Thus nothing needs to be done, prior to release.

Is it certain that all the packages in testing that depend on
libcommoncpp2-1.5-0 are using the old 1.5.1 ABI?  Apparently 1.5.3-1 didn't
bump shlibs either, because there are no reverse-deps waiting on it for
propogation...  Since this package was only 7 days old at the time of
freeze, odds are good that nothing built against the new ABI made it into
testing, but that's not a guarantee.

> > Upload the previous ABI stable release 1.5.1 with an epoc and await the
> > release of etch..

> I won't upload to unstable with an epoc..  Also please ignore, or rather just 
> leave in NEW, the last upload (1.5.3) which does correctly carry forward the 
> soname change.. But is not necessary for etch.

There's no reason that it needs to stay in NEW that I can see, but we don't
make that decision anyway. :)

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/