Re: Bug#402509: binNMU request Re: Bug#402509: twinkle crash on call end
tags 402509 =sid
On Sat, Jan 06, 2007 at 01:26:16PM +1100, Mark Purcell wrote:
> On Monday 11 December 2006 09:49, Mark Purcell wrote:
> > On Sunday 10 December 2006 21:48, Marcel Sebek wrote:
> > > I don't know which package upgrade caused this but it is something
> > > recent. When a call is finished, twinkle crashes with this error message
> > > on the console:
> > This is caused by the version of libcommoncpp2 (1.5.3-1) in unstable.
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402009
> Just an update.
> The solution for this problem is a library transition for libcommoncpp2. This
> is not necessary for etch as the current etch packages are stable and this
> bug has been tagged etch ignore.
Hmm, though it shouldn't have been; this isn't an etch-ignore issue, it's an
issue that's not present in etch at all ( -> tags: sid).
> Normally this happens automatically, but I suspect this has been suspended
> until the etch release.
> The updated version of libcommoncpp2 (1.5.3-2) is now in sid (unstable), but
> will not currently install with twinkle, nor a couple of dependencies.
> The version of libcommoncpp2 (1.5.1-4) in etch (testing) is good and should
> be used with twinkle until etch is released.
> The next steps to resolve this bug is:
> binNMU's of libccrtp, libzrtpcpp and twinkle.
> However, I suspect the release team will wait until after etch is released to
> turn back on automatic binNMU's.
There's nothing automatic about binNMUs, they're scheduled manually when
someone notices and brings it to the attention to the folks with wanna-build
At any rate, it seems new versions of twinkle, libccrtp, and libzrtpcpp have
already been uploaded to unstable, so this particular bug is already
resolved. The other packages still depending on libcommoncpp2-1.5-0 will be
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.