[bug-notifications] [pysvn 0004902]: pysvn and/or pythonsvn not functional
Mantis Bug Tracker
noreply at opencsw.org
Thu Feb 23 02:11:51 CET 2012
A NOTE has been added to this issue.
======================================================================
https://www.opencsw.org/mantis/view.php?id=4902
======================================================================
Reported By: joeymukherjee
Assigned To: dam
======================================================================
Project: pysvn
Issue ID: 4902
Category: upgrade
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2012-02-21 20:09 CET
Last Modified: 2012-02-23 02:11 CET
======================================================================
Summary: pysvn and/or pythonsvn not functional
Description:
In the Solaris 9 build, the pysvn and pythonsvn do not have core.py with
them. This makes the SVN python libs useless. The command I am trying to
get working is:
>>> from svn import core
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/opt/csw/lib/python/site-packages/svn/core.py", line 19, in
<module>
File "/opt/csw/lib/python/site-packages/libsvn/core.py", line 7, in
<module>
ImportError: No module named _core
======================================================================
----------------------------------------------------------------------
(0009640) maciej (manager) - 2012-02-23 02:11
https://www.opencsw.org/mantis/view.php?id=4902#c9640
----------------------------------------------------------------------
I'm thinking that Solaris 9 is a red herring, it doesn't matter, 9 or 11 or
10.
You'll see the problem when you look at the list of files in the package:
http://buildfarm.opencsw.org/pkgdb/srv4/f55304036900433c9aded3c2a35c0a67/
The files that are supposed to be in:
/opt/csw/lib/python/site-packages/svn
are in:
/opt/csw/lib/svn/python/site-packages/svn
...and the Python interpreter won't find them. The problem is with the way
the module is packaged.
You can temporarily work around that by setting PYTHONPATH to
/opt/csw/lib/svn/pythohn/site-packages, or making symlinks to
/opt/csw/lib/python/site-packages.
Looking at the build recipe, there's one line that causes the problem:
https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/subversion/trunk/Makefile
SVNLIB = $(prefix)/lib/svn
All paths, including Python, are relative to this one, and that's why
Python files end up under /opt/csw/lib/svn instead of /opt/csw/lib.
More information about the bug-notifications
mailing list