Thank you Stefan. I'll contact Wandisco. I couldn't find Python 2.7 for the RHEL from the libraries we have. But, I'll let roll back and wait on Wandisco Support. Was hoping someone else in community had experience with this before.
-----Original Message----- From: Stefan Sperling [mailto:s...@elego.de] Sent: Thursday, January 26, 2017 11:35 AM To: Michael Silberman <michael.silber...@netgear.com> Cc: Pavel Lyalyakin <pavel.lyalya...@visualsvn.com>; users@subversion.apache.org Subject: Re: Setup post-commit mailer fails On Thu, Jan 26, 2017 at 07:23:41PM +0000, Michael Silberman wrote: > Thank you! > I'm not sure how they installed the packages but assuming they used yum to do > it. > # yum list | egrep -i "svn|subversion" > acp-gfr-scripts-svn.noarch 1.7.4.1-56 installed > ltrace.x86_64 0.5-28.45svn.el6 > @anaconda-RedHatEnterpriseLinux-201604140956.x86_64/6.8 > mod_dav_svn.x86_64 1.9.4-1 > @/mod_dav_svn-1.9.4-1.x86_64 > subversion.x86_64 1.9.4-1 > @/subversion-1.9.4-1.x86_64 > subversion-debuginfo.x86_64 1.9.4-1 > @/subversion-debuginfo-1.9.4-1.x86_64 > subversion-fsfswd.x86_64 1.9.4-1 > @/subversion-fsfswd-1.9.4-1.x86_64 > subversion-javahl.x86_64 1.9.4-1 > @/subversion-javahl-1.9.4-1.x86_64 > svn-multisite-plus.x86_64 1:1.9.2.2-147 > @/svn-multisite-plus-1.9.2.2-147.x86_64 > eclipse-svnkit.x86_64 1.3.0-3.el6 > rhel-6-server-rpms > kmid.i686 2.0-0.14.20080213svn.el6 > rhel-6-server-rpms > kmid.x86_64 2.0-0.14.20080213svn.el6 > rhel-6-server-rpms > kmid-common.noarch 2.0-0.14.20080213svn.el6 > rhel-6-server-rpms > libdvdread.x86_64 4.1.4-0.3.svn1183.el6 > rhel-6-server-rpms > matchbox-window-manager.x86_64 1.2-6.20070628svn.1.el6 > rhel-6-server-rpms > sgabios-bin.noarch 0-0.3.20110621svn.el6 > rhel-6-server-rpms > subversion.i686 1.6.11-15.el6_7 > rhel-6-server-rpms > subversion-javahl.i686 1.6.11-15.el6_7 > rhel-6-server-rpms > svnkit.x86_64 1.3.0-3.el6 > rhel-6-server-rpms > > I downloaded the Python 2.7 tarball from > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.python.org_ft > p_python_2.7.13_Python-2D2.7.13.tgz&d=DwIBAg&c=mPqdMxlQPdltZylzF3sRPA& > r=3Cfm8zsX3deZqG3JCZLpFealAzwN9AMA_A7tQtJEAFY&m=Dv0gxKU1HhkAPMuDjqwvzr > LyGvn3V4_6h4luN4iS-f0&s=vTrgDL9hg-xEIBTiU8JycAkiR7QFMTRZ1A-ZiDzQ4UI&e= > I built it and installed alternate target. Why did you compile Python yourself from source? Was there no standard Python 2.7 RPM you could install in RHEL6? > I installed the RPM from > https://urldefense.proofpoint.com/v2/url?u=http-3A__opensource.wandisco.com_rhel_6_svn-2D1.9_RPMS_x86-5F64_subversion-2Dpython-2D1.9.4-2D1.x86-5F64.rpm&d=DwIBAg&c=mPqdMxlQPdltZylzF3sRPA&r=3Cfm8zsX3deZqG3JCZLpFealAzwN9AMA_A7tQtJEAFY&m=Dv0gxKU1HhkAPMuDjqwvzrLyGvn3V4_6h4luN4iS-f0&s=_VJ1uvTP0-t-g27bv4WrTyJGxjr_40BXCdb1PvHk7I0&e= > . > > Does this help? Is there another set of commands to run that would provide > more useful information? I think you should ask Wandisco's support to figure out what they would do to get the Python bindings running. (Perhaps someone else reading this list happens to know this -- I don't.) Generally, you should install the exact same things the distributor had installed on the system which compiled these packages. Anything else is a mix and match that can cause all sorts of problems.
