Your message dated Tue, 9 Jan 2007 04:38:44 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402509: binNMU request Re: Bug#402509: twinkle crash on
call end
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: twinkle
Version: 1:0.9-5
Severity: grave
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
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:
twinkle: symbol lookup error: twinkle: undefined symbol:
_ZN3ost6Thread9isRunningEv
I know that it is not caused by a new version of twinkle. However, I was
not able to determine if the source of the problem is libcommoncpp,
KDE or something else.
- -- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-ck1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages twinkle depends on:
ii kdelibs4c2a 4:3.5.5a.dfsg.1-5 core libraries and binaries for al
ii libasound2 1.0.13-1 ALSA library
ii libboost-regex1.33.1 1.33.1-9 regular expression library for C++
ii libc6 2.3.6.ds1-9 GNU C Library: Shared libraries
ii libccrtp1-1.5-0 1.5.0-2 Common C++ class framework for RTP
ii libcommoncpp2-1.5-0 1.5.3-1 A GNU package for creating portabl
ii libgcc1 1:4.1.1-21 GCC support library
ii libgcrypt11 1.2.3-2 LGPL Crypto library - runtime libr
ii libgnutls13 1.4.4-3 the GNU TLS library - runtime libr
ii libgsm1 1.0.10-13 Shared libraries for GSM speech co
ii libqt3-mt 3:3.3.7-1 Qt GUI Library (Threaded runtime v
ii libsndfile1 1.0.16-1 Library for reading/writing audio
ii libspeex1 1.1.12-2 The Speex Speech Codec
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.3-4 X11 client-side library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libzrtpcpp-0.9-0 0.9.0-2 ccrtp extension for zrtp/Zfone sup
ii zlib1g 1:1.2.3-13 compression library - runtime
twinkle recommends no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFfICvi2PKBl+Ic14RAsdaAKDWzKqqOHodyPzK+x+Vvh4UE/2r8QCg6boT
+NgpMARlYwStfggCnGN4cms=
=Ptnv
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
tags 402509 =sid
thanks
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
access.
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
binNMUed shortly.
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.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
