Re: Subversion commit email script and "unprintable" characters

2016-01-20 Thread Alfred von Campe
On Jan 20, 2016, at 11:29, Philip Martin wrote: > You encountered a packaging bug. WANdisco's Subversion 1.8 package for > RHEL/CentOS 6 is going to be rebuilt to have useable python bindings. Excellent, thanks for the update. I will wait for the next release and then try again. Alfred

Re: Subversion commit email script and "unprintable" characters

2016-01-20 Thread Philip Martin
Alfred von Campe writes: > It should not be this hard to run the > new mailer.py script on a RHEL/CentOS 6 system, especially since active > development on it appears to have stopped before RHEL 7 came out. You encountered a packaging bug. WANdisco's Subversion 1.8 package for RHEL/CentOS 6 is

Re: Subversion commit email script and "unprintable" characters

2016-01-20 Thread Alfred von Campe
On Jan 20, 2016, at 6:40, Philip Martin wrote: > The Subversion Python bits have been installed in the Python 2.6 tree > and really need to be in the Python 2.7 tree. On a CentOS 6 machine > with Python 2.7 installed via scl I can make things work by moving the > Python bits from the 2.6 location

Re: Subversion commit email script and "unprintable" characters

2016-01-20 Thread Philip Martin
Alfred von Campe writes: > On Jan 19, 2016, at 15:09, Philip Martin wrote: > >> I think that means your bindings were built against python 2.7, which >> provides PyCapsule_Import, while you are trying to use 2.6, which does >> not provide it. > > Thanks for the info. So how do I resolve this? I

Re: Subversion commit email script and "unprintable" characters

2016-01-19 Thread Alfred von Campe
On Jan 19, 2016, at 15:09, Philip Martin wrote: > I think that means your bindings were built against python 2.7, which > provides PyCapsule_Import, while you are trying to use 2.6, which does > not provide it. Thanks for the info. So how do I resolve this? I’m not a Python person, but I do kno

Re: Subversion commit email script and "unprintable" characters

2016-01-19 Thread Philip Martin
Alfred von Campe writes: > File "/usr/lib/python2.6/site-packages/libsvn/fs.py", line 22, in > swig_import_helper > _mod = imp.load_module('_fs', fp, pathname, description) > ImportError: /usr/lib/libsvn_swig_py-1.so.0: undefined symbol: > PyCapsule_Import I think that means your binding

Re: Subversion commit email script and "unprintable" characters

2016-01-19 Thread Alfred von Campe
On Jan 17, 2016, at 21:26, Daniel Shahaf wrote: > > Alfred von Campe wrote on Wed, Jan 13, 2016 at 20:54:12 -0500: >> Is there any documentation for this script (other than the script >> itself)? > > There's mailer.conf.example in the same directory. Thanks, Daniel, but I am trying to run this

Re: Subversion commit email script and "unprintable" characters

2016-01-17 Thread Daniel Shahaf
Alfred von Campe wrote on Wed, Jan 13, 2016 at 20:54:12 -0500: > Is there any documentation for this script (other than the script > itself)? There's mailer.conf.example in the same directory.

Re: Subversion commit email script and "unprintable" characters

2016-01-13 Thread Alfred von Campe
Thanks for that pointer. I’ve started to look into the new script, and noticed it has an accompanying config file. However, I would like to be able to specify some parameters on the command line because they vary with each commit. For instance, this is how I call the the old Perl script from

Re: Subversion commit email script and "unprintable" characters

2016-01-13 Thread Ryan Schmidt
On Jan 13, 2016, at 9:27 AM, Alfred von Campe wrote: > > We are using a (very old) commit-email.pl script to send out email > notifications from a post-commit hook on our Linux server running Subversion > 1.7.5. Lately I’ve noticed some emails that contain lots of “unprintable” > characters.

Subversion commit email script and "unprintable" characters

2016-01-13 Thread Alfred von Campe
We are using a (very old) commit-email.pl script to send out email notifications from a post-commit hook on our Linux server running Subversion 1.7.5. Lately I’ve noticed some emails that contain lots of “unprintable” characters. Here is a snippet from a recent commit: If it?\226?\128?\15