On 2014-08-13 23:06, Mark Phippard wrote:
> On Wed, Aug 13, 2014 at 5:00 PM, olli hauer <ohauer_at_gmx.de> wrote:
>> Upgraded a subversion-1.7.18 installation from http-2.2.28 to httpd-2.4.10
>> and running into strange issues.
>> Two clean builds (jail environment) with apr-1.5.1, apr-util-1.5.3,
>> subversion-1.7.18, a) httpd-2.2.28 and b) httpd-2.4.10
>> No issues on httpd-2.2.28 or by using the svn protocol only via webdav
>> (client independ)
> Not to hijack the thread off topic, but I am sure you are aware that httpd
> 2.2.x and 2.4.x are not binary compatible. So you will need a different
> set of SVN binaries built for each version? Or, if the APR etc. libs are
> all the same, then at least mod_dav_svn would need to be custom built for
Sure, therefore I setup two builds, one against a) httpd-2.2.28 and the second
against b) httpd-2.4.10.
Package building is one part of my work ;)
Removing all related packages changing the package repo and reinstall is done
in one minute.
> Did you consider trying 1.8.x? I recall there were some 2.4.x fixes made.
Yes, but unluckily 1.8 is no option at the moment, also this could be a
potential problem for RHEL7 based systems (they deliver with svn 1.7 and
> I assume those were backported to 1.7.x but do not remember.
Reading the Changelog it seems so, but i suspect some changes are missing
after the latest changes on the httpd-2.4 dav changes.
Received on 2014-08-13 23:19:27 CEST