Hi there,
I already browsed a few archives and excluded the proxy-thing. There
must be some incompatibility problems. The setup includes a host running
apache2 (.49, SuSE 9.1) and a single svn repository which I can access
locally via http. From another client (SuSE 8.2) I can't access the same
repository, but I can browse it ("svn: REPORT request failed on
'/repos/intelliframe/!svn/vcc/default'
svn: REPORT of '/repos/intelliframe/!svn/vcc/default': 400 Bad Request
(http://192.168.0.2)"), so it's no apache misconfiguration (took it from
README.SuSE, world readable, some users only commit)
The network configuration is easy: client (8.2)->100MBit->Switch->host
(9.1). Apache uses no virtual hosts, no proxy, only Firewall. Client
running on svn 1.0.7 and neon 0.24. (server-) host running on svn 1.0.0
and neon 0.24.
When accessing the repos from the foreing client via svn+ssh I get
another funky error message: "svn: relocation error:
/usr/lib/libsvn_ra_svn-1.so.0: undefined symbol:
apr_procattr_child_errfn_set". SSH is running, I use it for remote
administration (including ssh-agent).
Afterall it works using "svn://". Now what's going on with svn. Was
there a change in protocol from 1.0.0 to 1.0.7, did SuSE recompile some
packages? I cannot sync the package versions between both hosts. For 8.2
there is only 1.0.7 or some 0.24 and for 9.1 I also have to update
apache to .50 which breaks apache fully (segmentation fault).
May I increase log level of svn on server side to see why my request is bad?
Thanks for help...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 28 07:56:44 2004