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

On Mon, Mar 26, 2012 at 5:36 PM, Daniel Shahaf <danielsh_at_elego.de> wrote:

> "SVNAdvertiseV2Protocol off" might be a workaround.
>
> Note that there are known issues with httpd-2.4 support in svn with bdb
> repositories.
>

I could workaround with that but than I don't get the benefits of new
protocol.

Just to add I stumbled upon thins thread
http://mail-archives.apache.org/mod_mbox/httpd-users/201203.mbox/%3Cjkg3qq$a55$1@dough.gmane.org%3E

I am facing the exactly the same issue.

I wonder why wsgi and svn would conflict and create such scenario.

>
> vishwajeet singh wrote on Mon, Mar 26, 2012 at 15:13:16 +0530:
> > Hi All,
> >
> > I recently upgraded from subversion server from 1.6 to 1.7, everything
> > works fine for 1.6 client and 1.7 server.
> > But when I upgrade to 1.7 client my commit fails with following error
> >
> > *svn: E160013: Commit failed (details follow):*
> > *svn: E160013: '/svn/RDR/!svn/me' path not found*
> >
> > I am able to checkout and update with 1.7 client but not able to commit.
> >
> > My apache version is 2.3 and OS is centos 5.4.
> >
> > Any help in this regard is appreciated
> >
> > Regards,
> > Vishwajeet Singh
> > +91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
> > Twitter: http://twitter.com/vishwajeets | LinkedIn:
> > http://www.linkedin.com/in/singhvishwajeet
>

-- 
Vishwajeet Singh
+91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet