[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.2 client is incompatible with 1.1 mod_dav_svn

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-12-03 15:17:38 CET

"C. Michael Pilato" <cmpilato@collab.net> writes:

> Philip Martin <philip@codematters.co.uk> writes:
>> Using trunk I get this
>> $ svn co http://svn.collab.net/repos/svn/trunk/tools qq
>> $ svn sw http://svn.collab.net/repos/svn/trunk/tools/dev qq/dev
>> ../svn/subversion/libsvn_wc/lock.c:642: (apr_err=155005)
>> svn: Working copy '../svn/tools/iz' not locked
> This is intentional, and the dev-list was forewarned when I posted the
> patch for this change and let it sit for almost two weeks before
> committing.
> http://svn.haxx.se/dev/archive-2004-11/0724.shtml

With the subject "[PATCH] Issue #2124". I guess I ignored it as I
didn't realise it was important, it certainly didn't provoke any

> Be careful that what you *perceive* as 1.2-minus-r12006 as "working"
> truly is -- chances are very good that your wcprops contain incorrect
> version resource URLs. This hidden incorrectness causes at least
> working copies which actually don't work for many ra-dav operations,
> or worse, can actually cause commits to modify the wrong thing in the
> repository (an edge case, but possible). There are server bugs in 1.0
> and 1.1, but they were never triggered. The 1.1 client actually
> introduced this bad behavior by exposing the server bugs. It's
> complicated.
> The workaround for the problem you now see should be straightforward:
> (cd qq/dev; svn sw http://svn.collab.net/repos/svn/trunk/tools/dev)
> After long discussion with sussman, we agreed to move forward with the
> r12006 change because a visible bug with a simple workaround is far
> less of a problem than a hidden bug with a tricky workaround. And
> again, this was all described in the patch I posted.

I read the log of r12006. Perhaps it's just me, but it doesn't really
make the compatibilty problems explicit, it certainly doesn't mention
1.2 or 1.1. It doesn't mention the work-around either; I'm not sure
whether the workaround is appropriate for the log message, but putting
it there might ensure it gets into CHANGES.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 3 15:18:48 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.