[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: CentOS 8 Python bindings - opensource.wandisco.com

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Sun, 12 Apr 2020 13:09:38 -0400

On Sat, Apr 11, 2020 at 3:21 PM Jarkko Hyvärinen
<jarkkohyvarinen_at_hotmail.com> wrote:
>
> Hi
>
>
>
> I have installed Subversion 1.10.6 and python bindings (subversion-python) to CentOS 8 server from opensource.wandisco.com repo. My goal is to get Trac and Subversion working with CentOS 8.
>
>
>
> After installation I encoutered two problems with python bindings:
>
>
>
> If I run ----> ’python2 -c "from svn import core"’
>
> then ’ImportError: No module named _core’ raises
>
> If I specify PYTHONHOME and PYTHONPATH ----> ’PYTHONHOME=/usr PYTHONPATH=/usr/lib64/python2.7/site-packages/libsvn/ python2 -c "from svn import core"’
>
> then ’ImportError: /usr/lib64/libsvn_swig_py-1.so.0: undefined symbol: PyUnicode_FromFormat’ raises
>
> i. It seems that our CentOS 8 server has ’PyUnicodeUCS4_FromFormat’ instead of ’PyUnicode_FromFormat’
>
>
>
> Is there currently any workaround to this without building Subversion from source cod

Use python 3. Python 2 was partially, and poorly, abandoned for RHEL
8 and it's being phased out of RHEL 7 painfully and slowly. Take good
look at the Fedora SRPM's if you wnt to backport to RHEL 8. It's
tricky business. I used to publish the rpmforge RPMs for Subversion,
and backporting got *paindul* due to various library dependencies
which notably exceeded those of the OS.
Received on 2020-04-12 19:10:01 CEST

This is an archived mail posted to the Subversion Users mailing list.