Your message dated Thu, 21 Apr 2005 14:59:29 +0900 (JST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#285079: Ping
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Dec 2004 14:53:26 +0000
>From [EMAIL PROTECTED] Fri Dec 10 06:53:26 2004
Return-path: <[EMAIL PROTECTED]>
Received: from iliveon.earth.li (pot.noodles.at.earth.li) [217.147.80.1] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Ccm98-0003ZZ-00; Fri, 10 Dec 2004 06:53:26 -0800
Received: from noodles by pot.noodles.at.earth.li with local (Exim 4.34)
        id 1Ccm7G-0005tz-AE; Fri, 10 Dec 2004 14:51:30 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jonathan McDowell <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libosip2 2.0.9 breaks siproxd
X-Mailer: reportbug 3.4
Date: Fri, 10 Dec 2004 14:51:30 +0000
X-Debbugs-Cc: Debian VoIP Team <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
        X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: libosip2
Version: 2.0.9-1
Severity: grave
Justification: renders package unusable

The new libosip2 2.0.9 package, which I upgraded to this morning, seems
to break siproxd, with the error:

/usr/sbin/siproxd: relocation error: /usr/sbin/siproxd: undefined symbol: 
osip_free

Looking at the old 2.0.6 lib compared to 2.0.9:

[EMAIL PROTECTED] ~]$ nm -D /usr/lib/libosip2.so.2.0.6 | grep osip_free
         U osip_free
[EMAIL PROTECTED] ~]$ nm -D libosip2.so.2.0.9 | grep osip_free
[EMAIL PROTECTED] ~]$ 

This looks like the ABI has changed between 2.0.6 and 2.0.9. Shouldn't
the soname have also changed or do I misunderstand that problem?

Dropping back to 2.0.6 makes siproxd work for me again.

siproxd version is 0.57.snap040720-2

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-rc3
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages libosip2 depends on:
ii  libc6                       2.3.2.ds1-19 GNU C Library: Shared libraries an

-- no debconf information

---------------------------------------
Received: (at 285079-done) by bugs.debian.org; 21 Apr 2005 05:59:17 +0000
>From [EMAIL PROTECTED] Wed Apr 20 22:59:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c158130.vh.plala.or.jp (mvs2.plala.or.jp) [210.150.158.130] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DOUib-00009c-00; Wed, 20 Apr 2005 22:59:17 -0700
Received: from msc2.plala.or.jp ([172.23.8.25]) by mvs2.plala.or.jp
          with ESMTP
          id <[EMAIL PROTECTED]>
          for <[EMAIL PROTECTED]>;
          Thu, 21 Apr 2005 14:59:07 +0900
Received: from cfard.araki.net ([210.158.216.125]) by msc2.plala.or.jp
          with ESMTP
          id <[EMAIL PROTECTED]>
          for <[EMAIL PROTECTED]>;
          Thu, 21 Apr 2005 14:59:06 +0900
Received: from localhost (localhost [127.0.0.1])
        by cfard.araki.net (Postfix) with ESMTP id E3846171C8
        for <[EMAIL PROTECTED]>; Thu, 21 Apr 2005 14:59:29 +0900 (JST)
Date: Thu, 21 Apr 2005 14:59:29 +0900 (JST)
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#285079: Ping
From: ARAKI Yasuhiro <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
X-Mailer: Mew version 4.0.65 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Hi,
I believe #285079 was fixed at 285178-close.

At Debian Bug report logs - #285079, libosip2 2.0.9 breaks siproxd

and 

Debian Bug report logs - #285178, libosip2 2.0.9 breaks siproxd

is same problem.


#285178 is already closed at "Sun, 20 Mar 2005 16:02:55 -0500" by uploaded
siproxd (1:0.5.10-1). It use libosip2-3. 

> Hi samuel,
> 
> Now I uploaded libosip2_2.0.9-4+2.0.6_i386.deb to debian queue.
> 
> libosip2_2.0.9-4+2.0.6 made from libosip2-2.0.6.
> And it includes fix for "URI Parsing Heap Overflows. Reported at 
> http://www.securiteam.com/securitynews/5RP0B20FFG.html";.
> 
> Thanks.
> 
> --
> ARAKI Yasuhiro 
> A Debian Official Developer <[EMAIL PROTECTED]>
>  
> 
> From: Samuel Mimram <[EMAIL PROTECTED]>
> Subject: Bug#285079: Ping
> Date: Wed, 20 Apr 2005 17:49:01 +0200
> 
> > ARAKI Yasuhiro wrote:
> > > Samuel,
> > > 
> > >>Hi,
> > >>
> > >>I'm just pinging the BR just to know how the issue of ABI-breakage of
> > >>libosip2 is going on since it blocks my package linphone (no news since
> > >>Dec 2004).
> > > 
> > > 
> > > As you packaged "linphone" (at least linphone_1.0.1-3) depends
> > > NEW ABI package of libosip2 is installed in Debian as "libosip2-3".
> > > 
> > > Do you want to use libosip2(<= 2.0.6)'s ABI?
> > 
> > I don't want to use libosip2 but this RC bug on it prevents libosip2-3 
> > from entering testing. See:
> > 
> > http://bjorn.haxx.se/debian/testing.pl?package=libosip2-3
> > 
> > Regards,
> > 
> > Samuel.
> > 
> > 
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to