[PATCH] Send path with lock token to fix issue 4369
From: Philip Martin <philip.martin_at_wandisco.com>
Date: Fri, 31 May 2013 19:40:40 +0100
http://subversion.tigris.org/issues/show_bug.cgi?id=4369
If I have broken locks the commit fails:
svnadmin create repo
With 1.8/serf
svn: E175002: Commit failed (details follow):
With 1.7/neon
svn: E195022: File '/home/pm/sw/subversion/obj/wc/A/f' is locked in another working copy
The reason appears to be that 1.8/serf sends lock tokens in If headers
If: (<opaquelocktoken:d5b2cb02-34e1-4893-ba8d-ccbcc22fd953>)
and apache responds with a 412 while 1.7/neon sends an URI:
If: <http://localhost:9630/obj/repo/A/f> (<opaquelocktoken:ad688167-ca91-43b9-9d28-f3b8b672ecb9>)
and apache responds with a 423.
What sort of URI do we have to supply? Will a session relative <f> do?
How about this for server relative:
Index: subversion/libsvn_ra_serf/commit.c
-- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/downloadReceived on 2013-05-31 20:41:15 CEST |
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.