On Mon, Sep 12, 2011 at 8:16 AM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Nico Kadel-Garcia wrote on Mon, Sep 12, 2011 at 07:20:18 -0400: >> On Mon, Sep 12, 2011 at 6:30 AM, Daniel Shahaf <d...@daniel.shahaf.name> >> wrote: >> > Felipe Alvarez wrote on Mon, Sep 12, 2011 at 10:31:22 +1000: >> >> Client: windows 7 x86_64 TortoiseSVN 1.5.9 (this version is REQUIRED!) >> >> Server: Redhat 4 svn version 1.4.4 ( r25188 ) (this version is REQUIRED!) >> >> >> > >> > These versions are ancient, unsupported, and contain known security holes. >> > >> >> Error Logs: >> >> apache error_log: A failure occurred while driving the update report >> >> editor >> >> apache error_log: Provider encountered an error while streaming a >> >> REPORT response. >> > >> > Run tools/dev/which-error.py on the six-digit number in the above error >> > message. >> >> Felipe, note that it's not "Red Hat 4". Red Hat 4.0 was published in >> 1996. Red Hat Enterprise Linux 4.0, commonly referred to as RHEL 4.0, >> was published in 2005. It is very painful to backport Subversion 1.6.x >> to RHEL 4, due to dependencies on more recent Python for >> configuration, and more recent swig and sqlite libraries for >> operation, > > Python is not required for building from a source tarball. > > SWIG is only required for some of the bindings, and SQLite is optional > on the server side (though it's mandatory on the client side in 1.7).
Try running "autoconf" and "./configure" on RHEL 4. It's nasty. I've been publishing the updates to releases on RPMforge, and it's gotten nasty. I don't know of anyone doing ongoing backports to RHEL 4.
