Re: Error after subversion upgrade

Swan, Nicole schrieb:

> The upgrade was indeed done correctly. (Of course, my problem was that I couldn't get in contact with the person who did the upgrade -- he works remotely.)
>
> I did finally get in contact with him, and we figured out that the problem seems to be related to having the repos configured to the root of Apache.
>
> In the following error notice the path:
>
> commits with fail with:
> svn: applying log message to
> //!svn/wbl/dafd7a36-77dd-0310-8dd8-f106bb595ebe/1658: 404 Not Found (....)
>
> There are two slashes. Thus the server replies with http://ourserver.com:8080//!svn... and thus the 404 error. A workaround of moving the repository from / to /svn makes it work correctly. A bug was submitted: http://subversion.tigris.org/issues/show_bug.cgi?id=1934
>
Hi,

I updated from svn 1.0.0 to 1.0.5 on my SuSE-box and had a similar error.

I solved the error with upgrading the libapr (and apache2) to the newest
version (in my case 2.0.49) and it worked.

Kind regards,

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 23 08:43:34 2004