Your message dated Mon, 16 May 2005 15:36:32 +0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#308766: jabber-irc: Depends: python2.3, but invokes 
/usr/bin/python
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; 5 May 2005 02:33:09 +0000
>From [EMAIL PROTECTED] Wed May 04 19:33:09 2005
Return-path: <[EMAIL PROTECTED]>
Received: from host1.quantact.com (fire.originalgangsters.org) [64.142.109.150] 
(postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DTWAn-000300-00; Wed, 04 May 2005 19:33:09 -0700
Received: by fire.originalgangsters.org (Postfix, from userid 1000)
        id B0EC013D64; Thu,  5 May 2005 03:44:38 +0100 (BST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mikael Karon <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: jabber-irc: crashes when trying to register transport
X-Mailer: reportbug 3.11
Date: Thu, 05 May 2005 03:44:38 +0100
Message-Id: <[EMAIL PROTECTED]>
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: jabber-irc
Version: 0.1cvs20050311-1
Severity: grave
Justification: renders package unusable

When trying to register with the transport this is the last thing I see
on the screen (launched it manually in order to see output)

DEBUG: socket       got   <iq type='set' id='sd272' 
to='irc.jabber.originalgangsters.net' from='[EMAIL PROTECTED]/Pandion'><query 
xmlns='jabber:iq:register' 
xml:lang='sv'><username>OG</username><password/><nick>DrOliver</nick><key/></query></iq>
DEBUG: dispatcher   ok    Got iq stanza
DEBUG: dispatcher   ok    Dispatching iq stanza with type->set 
props->[u'jabber:iq:register'] id->sd272
Traceback (most recent call last):
  File "/usr/sbin/jabberd-irc", line 1208, in ?
    connection.Process(1)
  File "/usr/lib/python2.3/site-packages/xmpp/dispatcher.py", line 105, in 
Process
    self.Stream.Parse(data)
  File "/usr/lib/python2.3/site-packages/xmpp/simplexml.py", line 331, in endtag
    self.dispatch(self._mini_dom)
  File "/usr/lib/python2.3/site-packages/xmpp/dispatcher.py", line 248, in 
dispatch
    handler['func'](session,stanza)
  File "/usr/sbin/jabberd-irc", line 769, in xmpp_iq_register_set
    if event.getQueryPayload().getTag('remove'):
AttributeError: 'list' object has no attribute 'getTag'

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1um
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages jabber-irc depends on:
ii  jabber-common                 0.4        Jabber server and transport (commo
ii  python2.3                     2.3.5-3    An interactive high-level object-o
ii  python2.3-irclib              0.4.4-1    IRC client library for Python
ii  python2.3-xmpp                0.2-rc1-1  Python library for communication w

-- no debconf information

---------------------------------------
Received: (at 307734-done) by bugs.debian.org; 16 May 2005 11:37:07 +0000
>From [EMAIL PROTECTED] Mon May 16 04:37:07 2005
Return-path: <[EMAIL PROTECTED]>
Received: from host-80-95-32-178.leasedlines.sura.ru (penza-gsm.ru) 
[80.95.32.178] 
        by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
        id 1DXduF-0008Cy-00; Mon, 16 May 2005 04:37:07 -0700
Received: (qmail 20968 invoked from network); 16 May 2005 11:36:35 -0000
Received: from unknown (HELO snake) (192.168.0.20)
  by fileserver.penza-gsm.ru with SMTP; 16 May 2005 11:36:34 -0000
From: Alexey Nezhdanov <[EMAIL PROTECTED]>
To: Steve Langasek <[EMAIL PROTECTED]>,
 debian-release@lists.debian.org
Subject: Re: Bug#308766: jabber-irc: Depends: python2.3, but invokes 
/usr/bin/python
Date: Mon, 16 May 2005 15:36:32 +0400
User-Agent: KMail/1.7.2
Cc: [EMAIL PROTECTED],
 [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
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: 

Thursday, 12 May 2005 12:32 Steve Langasek wrote:
> Package: jabber-irc
> Version: 0.1cvs20050311-1
> Severity: serious
>
> Hi Alexey,
>
> I was preparing to sponsor your upload of jabber-irc 0.1cvs20050420-1 to
> fix RC bug #307734, but in the process, lintian spit out this error:
>
>   E: jabber-irc: python-script-but-no-python-dep ./usr/sbin/jabberd-irc
>
> This is a missing dependency, and therefore an RC policy violation (and a
> violation of the python policy in particular).  Please fix this bug.
>
> In the meantime, since bug #307734 has now been open for a week, jabber-irc
> will be removed from testing.
Both bugs were fixed in the recent upload to archive ([2005-05-14] Accepted 
0.1cvs20050420-3 in unstable).
In the meantime package was removed from sarge.
Steve, is there any chance to get it back? This package have found several 
users during a half-year life in debian archive. I think it will be good 
thing (TM) to allow it find some more users.

This update contains only grave severity fixes: #307734 and several similar 
causing the very same crash under certain conditions.

-- 
Respectfully
Alexey Nezhdanov


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

Reply via email to