Problems using the Python bindings with Trac on SuSE 9.1
From: Bryan Dyck <bdyck_at_mac.com>
Date: 2004-07-28 21:42:41 CEST
Hi all..
I'll preface my plea for help by noting that this is perhaps not a 'core' Subversion issue, but I'm really at my wits' end here. I posted to the Trac dev list a couple days ago, but that seems to be extremely low-traffic at the moment, and I am not a Python hacker of any note... :)
In any case, the problem is as follows: I've been running Subversion for quite some time, and Trac seems to be getting increasing notice in various Subversion-related places, which is handy as I'm looking for a decent (and free :) issue tracker. It also offers some interesting features that really appeal to me over other solutions out there...
I installed Trac 0.71 just fine to its default install location, and decided to locate the project environment under /srv/www/trac. When I run
trac-admin /srv/www/trac initenv
I get the following Python traceback immediately after entering my project name:
Traceback (most recent call last):
I am running Subversion 1.0.5, which I built from sources. I included the '--enable-swig-bindings=java,ptyhon' configure switch, and the location of where SuSE installs SWIG as well as running the commands for building the Python SWIG bindings after Subversion was installed. Subversion itself is installed in the default location, /usr/local/.
Any help would be greatly appreciated, polite Clue Stick whackings for general silliness included. Thanks!
Cheers,
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.