I installed www-apps/trac-0.8.4 on my AMD64 gentoo box, however when I try to run 'trac-admin' I recieve: Traceback (most recent call last): File "/usr/bin/trac-admin", line 34, in ? from trac import sync File "/usr/lib64/python2.3/site-packages/trac/sync.py", line 22, in ? from svn import core, fs, delta, repos ImportError: No module named svn The python hooks installed by the subversion package are located in /usr/lib64/svn-python, which by default is not in python's sys.path. On my x86 32-bit box the subversion hooks are located in /usr/lib/python2.3/site-packages/svn which is contained within python's sys.path, so everything works fine there. To work around this, I created a file called "svn.pth" located in /usr/lib64/python2.3/site-packages which contains a single line: /usr/lib64/svn-python/ Alternativley, a symbolic link could be made, or the subversion modules could be installed to the python site package directory as is done on x86. Reproducible: Always Steps to Reproduce: 1. emerge trac subversion python 2. issue the trac 'trac-admin' command 3. Actual Results: Traceback (most recent call last): File "/usr/bin/trac-admin", line 34, in ? from trac import sync File "/usr/lib64/python2.3/site-packages/trac/sync.py", line 22, in ? from svn import core, fs, delta, repos ImportError: No module named svn Expected Results: Executed the program without error.
Python folks, please advise.
Shortcut might be: ln -s /usr/lib64/svn-python/svn /usr/lib64/python2.3/site-packages/svn ln -s /usr/lib64/svn-python/libsvn /usr/lib64/python2.3/site-packages/libsvn
Fraser, which profile are you using? please post your emerge info
I masked trac and two of it's required packages (silvercity and clearsilver) to get it installed. I have trac installed cleanly and it is running without a problem. It looks like whatever requirement in python that was causing a problem is now fixed. I would recommend unmasking these packages for amd64 and closing this bug.
can't reproduce it with trac-0.9.2, assuming the new version fixed that issue. please reopen if you still suffer from this bug