Package: python2.3-subversion Version: 1.1.3-2 Severity: normal I am filing this bug against the python2.3-subversion package, instead of the trac package, because I believe this package is where the problem can be fixed. I may, however, be wrong about this.
The problem is that after upgrading to the seen revisions of Trac and Subversion, the Trac revision logs break by the error message: Fatal Python error: PyThreadState_Get: no current thread This comes from a seemingly correct code invocation. Trac is invoked from apache as a cgi-program written in python, which accesses the subversion repository. This all worked with trac 0.8-1 and subversion 1.1.3-1. I have no real idea what causes the problem, but a possible culprit is the transition to a newer swig, which generates the python bindings. Subversion 1.1.3-1 was compiled with swig 1.3.22, where as Subversion 1.1.3-2 was compiled with swig 1.3.24. ii trac 0.8.1-1 Enhanced wiki and issue tracking system for -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7-aka-1 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages python2.3-subversion depends on: ii libapr0 2.0.53-5 the Apache Portable Runtime ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libsvn0 1.1.3-2 shared libraries used by Subversio ii python2.3 2.3.5-1 An interactive high-level object-o ii subversion 1.1.3-2 advanced version control system (a -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
