Cannot convert subversion repository
Patrick Mézard
pmezard at gmail.com
Thu Nov 15 09:07:55 CST 2007
Kim Tiedemann a écrit :
> Hi Patrick,
>
>> I do not think the Windows mercurial package can use external modules like the python bindings. The bindings are not shipped under Windows because of packaging issues. That may change in the future. In the meantime, you should try building mercurial from sources which is easy if you already know how to build python extensions for your environment.
>>
>> Can you try the same command from Linux ?
>>
>
> Yes:
>
[snip]
> So it seems that the python subversion bindings cannot be loaded. If I
> try the python command:
>
> from svn.core import SubversionException, Pool
>
> I get the following error:
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/lib/python2.4/site-packages/svn/core.py", line 19, in ?
> from libsvn.core import *
> File "/usr/lib/python2.4/site-packages/libsvn/core.py", line 4, in ?
> import _core
> ImportError: /usr/lib/libsvn_swig_py-1.so.0: undefined symbol:
> svn_commit_info_dup
>
> So it seems that something is wrong with the bindings. But
> unfortunately I am a Linux newbie - so I am a bit lost :-(
Your bindings are probably too old (and there might be something wrong too with your setup), try upgrading them. I know the convert extension runs fine with 1.4.5, I am unsure for older versions.
--
Patrick Mézard
More information about the Mercurial
mailing list