[email protected]
[Top] [All Lists]

Bug#298888: marked as forwarded (libsvn0: breaks log feature in python l

Subject: Bug#298888: marked as forwarded libsvn0: breaks log feature in python libsvn
From: Debian Bug Tracking System
Date: Thu, 17 Mar 2005 02:04:51 -0800
Your message dated Thu, 17 Mar 2005 10:59:24 +0100
with message-id <[email protected]>
has caused the Debian Bug report #298888,
regarding libsvn0: breaks log feature in python libsvn
to be marked as having been forwarded to the upstream software
author(s) [email protected]

(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 299817-forwarded) by bugs.debian.org; 17 Mar 2005 10:00:18 +0000
>From [email protected] Thu Mar 17 02:00:18 2005
Return-path: <[email protected]>
Received: from tms.rz.uni-kiel.de [] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DBrnd-0000V1-00; Thu, 17 Mar 2005 02:00:17 -0800
Received: from amavis by tms.rz.uni-kiel.de with scanned-ok (Exim 4.34)
        id 1DBrnT-0003Ih-6a
        for [email protected]; Thu, 17 Mar 2005 11:00:07 +0100
Received: from zaphod.gpi.uni-kiel.de ([])
        by tms.rz.uni-kiel.de with esmtp (Exim 4.34)
        id 1DBrnQ-0003II-RX
        for [email protected]; Thu, 17 Mar 2005 11:00:04 +0100
Received: from localhost ([] helo=stargate.galaxy)
        by zaphod.gpi.uni-kiel.de with esmtp (Exim 3.35 #1 (Debian))
        id 1DBrnQ-0000Fo-00
        for <[email protected]>; Thu, 17 Mar 2005 11:00:04 +0100
Received: by stargate.galaxy (Postfix, from userid 1000)
        id 23D4018830; Thu, 17 Mar 2005 11:00:03 +0100 (CET)
Resent-From: [email protected]
Resent-Date: Thu, 17 Mar 2005 11:00:03 +0100
Resent-Message-ID: <[email protected]>
Resent-To: [email protected]
Date: Thu, 17 Mar 2005 10:59:24 +0100
From: Torsten Landschoff <[email protected]>
To: [email protected]
Subject: Breakage in subversion with new runtime (1.3.24)
Message-ID: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040722i
X-Virus-Scanned: by AMaViS 0.3.12 (Uni-Kiel/tms)
Resent-Date: Thu, 17 Mar 2005 11:00:07 +0100
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 

Hi there, 

Debian users have reported about a swig related problem which breaks the
python bindings of subversion. I don't want to repeat all information,
just the basics:

- Trac (a lightweight version resembling something like source forge)
  uses the python bindings of subversion for repository access
- Upgrading subversion to the latest version breaks trac
- The only change from subversion 1.1.3-1 to 1.1.3-2 (Debian revisions)
  was to move from swig 1.3.22 to swig 1.3.24

For more information please have a look at the report logs at


I built a debugging version of subversion to find out where the problem
is located and got this backtrace out of gdb:

(gdb) bt
#0  0xb7e827ab in raise () from /lib/tls/libc.so.6
#1  0xb7e83f12 in abort () from /lib/tls/libc.so.6
#2  0x080d94a9 in Py_FatalError ()
#3  0x080d76ef in PyThreadState_Get ()
#4  0x080ad18b in PyEval_GetGlobals ()
#5  0x080cdffb in PyImport_Import ()
#6  0x080cd407 in PyImport_ImportModule ()
#7  0x080f69dc in PyCObject_Import ()
#8  0xb794ca81 in SWIG_Python_GetTypeListHandle () at pyrun.swg:731
#9  0xb794edf0 in SWIG_Python_GetTypeList () at pyrun.swg:747
#10 0xb794edce in SWIG_Runtime_TypeQuery (name=0xb794f36b 
"svn_log_changed_path_t *") at runtime.swg:20
#11 0xb794eba7 in svn_swig_py_log_receiver (baton=0xb7dd9c84,
        changed_paths=0x829a4a8, rev=1, author=0x829e728 "www-data",
        date=0x82b8ba0 "2005-03-17T08:59:07.102288Z", msg=0x82cd200 "Test",
        pool=0x829a410) at
#12 0xb7454544 in svn_repos_get_logs2 (repos=0x8275e10, paths=0x82771b0,
        start=0, end=1, discover_changed_paths=1, strict_node_history=0,
        authz_read_func=0, authz_read_baton=0x0, receiver=0xb794eb81
        <svn_swig_py_log_receiver>, receiver_baton=0xb7dd9c84,
        pool=0x8275bf0) at subversion/libsvn_repos/log.c:411
#13 0xb74545fd in svn_repos_get_logs (repos=0x8275e10, paths=0x82771b0,
        start=0, end=1, discover_changed_paths=1, strict_node_history=0,
        receiver=0xb794eb81 <svn_swig_py_log_receiver>,
        receiver_baton=0xb7dd9c84, pool=0x8275bf0) at
#14 0xb749a0e3 in _wrap_svn_repos_get_logs (self=0x0, args=0x1) at 
#15 0x080fde6a in PyCFunction_Call ()

The line in question in swigutil_py.c (1276) is

  swig_type_info *tinfo = SWIG_TypeQuery("svn_log_changed_path_t *");

At that point python aborts with the message 

  Fatal Python error: PyThreadState_Get: no current thread

As it worked with swig 1.3.22 I think this might be a bug introduced by
the new runtime. OTOH having a C language callback run SWIG_TypeQuery
might not be supported which would mean that the C code has to be fixed. 

What do you think is the way to fix this?



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

<Prev in Thread] Current Thread [Next in Thread>
  • Bug#298888: marked as forwarded (libsvn0: breaks log feature in python libsvn), Debian Bug Tracking System <=