Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Philip Martin <philip.martin_at_wandisco.com> writes:

> vishwajeet singh <dextrous85_at_gmail.com> writes:
>
>> As thread it's not just with mod_wsgi, problem persist with fcgi, can you
>> please elaborate on reordering I tried moving wsgi module at end but that
>> did not help.
>
> Reordering may not work; it depends how the other modules work. Fixing
> it may require code changes in the non-Subversion modules. The error
> message:
>
> svn: E160013: '/svn/RDR/!svn/me' path not found
>
> is exactly what happens when some other module intercepts POST requests
> intended for mod_dav_svn.

I've just added mod_wsgi 3.3-2 to my test environment and Subversion's
v2 protocol still works. This is a Subversion commit over v2:

::1 - - [27/Mar/2012:12:04:18 +0100] "OPTIONS /obj/repo HTTP/1.1" 200 188
::1 - - [27/Mar/2012:12:04:18 +0100] "POST /obj/repo/!svn/me HTTP/1.1" 201 -
::1 - - [27/Mar/2012:12:04:18 +0100] "PROPPATCH /obj/repo/!svn/txn/16-h HTTP/1.1" 207 426
::1 - - [27/Mar/2012:12:04:18 +0100] "MKCOL /obj/repo/!svn/txr/16-h/A HTTP/1.1" 201 199
::1 - - [27/Mar/2012:12:04:18 +0100] "MERGE /obj/repo HTTP/1.1" 200 424

This is mod_wsgi request:

::1 - - [27/Mar/2012:12:04:22 +0100] "GET /myapp HTTP/1.1" 200 12

I used a very basic mod_wsgi configuration, just a line:

WSGIScriptAlias /myapp /home/pm/sw/subversion/obj/myapp.wsgi

I suggest you setup a test environment with a working Subversion config.
Gradually extend it with mod_wsgi until it stops working. Then tell us,
and/or the mod_wsgi people, which config change causes Subversion to
fail.

-- 
Philip