subversion probem moving from 1.2.0 to 1.4.2

Yesterday, I had emailed the list with a problem upgrading subversion
from 1.2.0 (running apache 2.0 and bdb) to 1.4.2 (running apache 2.2 and
fsfs). Fortunately, it seems, that I solved that problem on my own. As
it happens, I was using the apr that comes with the subversion-deps
package which was not compatible with Apache 2.2. I wonder if the
"configure" script should check whether the version of apr being used is
compatible with the web server. This would have saved me a lot of time.

Now that I have that "working", I have one problem, and one question
that I am hoping someone can help me with ...

1) When I try to "checkout" an empty repository that I just created on
the subversion server, I get:

svn checkout http://myhost.cse.yorku.ca:1234/repos/newjas
Authentication realm: <http://myhost.cse.yorku.ca:1234> Subversion
Repository
Password for 'jas':
svn: REPORT request failed on '/repos/newjas/!svn/vcc/default'
svn: REPORT of '/repos/newjas/!svn/vcc/default': 400 Bad Request
(http://myhost.cse.yorku.ca:1234)

.. in the web server log file, I see:

[time/date] [error] [client X] The request body must specify a report.

Also,

2) Since I had to recompile my subversion server to use the version of
APR that comes with Apache 2.2, will my Windows clients be able to use
the existing subversion binaries from the tigris site, or does the
Windows subversion server need to be recompiled as well in order to be
compatible with the server APR version?

Thanks in advance for any help that you can provide...

Jason.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 16 20:58:10 2006