Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of danellis10@gmail.com
 designates 74.125.82.181 as permitted sender)
MIME-Version: 1.0
Date: Tue, 20 May 2014 15:02:49 -0700
Message-ID: 
 <CAJUNwvPcn-MwQt+4jQvnrobeOVA0HQ8==TO1CGyfy9hOWZ06HA@mail.gmail.com>
Subject: Incorrect error message on svn copy? Advice?
From: Dan Ellis <danellis10@gmail.com>
To: Subversion Users <users@subversion.apache.org>
Content-Type: multipart/alternative; boundary=f46d044288026fa80204f9dc0aa6

--f46d044288026fa80204f9dc0aa6
Content-Type: text/plain; charset=UTF-8

Hi,

I'm wondering if I'm getting an incorrect error message...

I'm attempting to copy a file from a working copy to the server, but using
an incorrect case for one of the folders in the path.  The paths all exist
and everything works fine using correct case.  In the example below, "FOO"
exists on the server as "foo".

(Case 1)
c:\Project_files\sandbox>svn copy bar.c
http://svr/repo/some_project/FOO/bar.c -m "text commit"
Adding copy of        bar.c
svn: E155011: Commit failed (details follow):
svn: E155011: File 'C:\Project_files\sandbox\bar.c' is out of date
svn: E160013: File not found: transaction '4249-3lp', path
'/some_project/FOO/bar.c'

If I correctly use "foo" instead of "FOO", I get the expected response:

(Case 2)
c:\Project_files\sandbox>svn copy bar.c
http://svr/repo/some_project/foo/bar.c -m "test commit"
Adding copy of        bar.c

Committed revision 4249.

If I use --parents to create the path (in case it doesn't exist):

(Case 3)
c:\Project_files\sandbox>svn copy --parents bar.c
http://svr/repo/some_project/FOO/bar.c -m "test commit"
Adding copy of        bar.c
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
** ERROR-CASE: This repository is set to be case insensitive.
** ERROR-CASE: Clash: '/some_project/FOO' '/some_project/foo'

It appears we are using a server-side script to prevent name clashes (since
we are using windows clients) on our server in Case 3.  Why would Case 3
get caught (--parents) but Case 1 seem to slip by this server side script
and return a different error?  I assume we're using the
stock case-insensitive.py, but regardless, I don't understand the behavior
difference.

As I would expect, I cannot perform an "svn info" on the incorrect-cased
path.  I was hoping I could do an "svn info" to test/determine what the
case corrected path is, but will have to try an "svn copy --parents" first
and if it fails due to a case clash, retry with the returned clash info.
 Is there a better way to accomplish this?  I do understand this is more of
a corner use case, especially since Subversion is (properly IMO) designed
around case sensitivity.

Thanks,
Dan

--f46d044288026fa80204f9dc0aa6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I&#39;m wondering if I&#39;m gettin=
g an incorrect error message...</div><div><br></div><div>I&#39;m attempting=
 to copy a file from a working copy to the server, but using an incorrect c=
ase for one of the folders in the path. =C2=A0The paths all exist and every=
thing works fine using correct case. =C2=A0In the example below, &quot;FOO&=
quot; exists on the server as &quot;foo&quot;.</div>
<div><br></div><div>(Case 1)</div><div><div>c:\Project_files\sandbox&gt;svn=
 copy bar.c <a href=3D"http://svr/repo/some_project/FOO/bar.c">http://svr/r=
epo/some_project/FOO/bar.c</a> -m &quot;text commit&quot;</div><div>Adding =
copy of =C2=A0 =C2=A0 =C2=A0 =C2=A0bar.c</div>
<div>svn: E155011: Commit failed (details follow):</div><div>svn: E155011: =
File &#39;C:\Project_files\sandbox\bar.c&#39; is out of date</div><div>svn:=
 E160013: File not found: transaction &#39;4249-3lp&#39;, path &#39;/some_p=
roject/FOO/bar.c&#39;</div>
</div><div><br></div><div>If I correctly use &quot;foo&quot; instead of &qu=
ot;FOO&quot;, I get the expected response:</div><div><div><br></div><div>(C=
ase 2)</div><div>c:\Project_files\sandbox&gt;svn copy bar.c <a href=3D"http=
://svr/repo/some_project/foo/bar.c">http://svr/repo/some_project/foo/bar.c<=
/a> -m &quot;test commit&quot;</div>
<div>Adding copy of =C2=A0 =C2=A0 =C2=A0 =C2=A0bar.c</div><div><br></div><d=
iv>Committed revision 4249.</div></div><div><br></div><div>If I use --paren=
ts to create the path (in case it doesn&#39;t exist):</div><div><div><br></=
div><div>(Case 3)</div>
<div>c:\Project_files\sandbox&gt;svn copy --parents bar.c <a href=3D"http:/=
/svr/repo/some_project/FOO/bar.c">http://svr/repo/some_project/FOO/bar.c</a=
> -m &quot;test commit&quot;</div><div>Adding copy of =C2=A0 =C2=A0 =C2=A0 =
=C2=A0bar.c</div><div>
svn: E165001: Commit failed (details follow):</div><div>svn: E165001: Commi=
t blocked by pre-commit hook (exit code 1) with output:</div><div>** ERROR-=
CASE: This repository is set to be case insensitive.</div><div>** ERROR-CAS=
E: Clash: &#39;/some_project/FOO&#39; &#39;/some_project/foo&#39;</div>
</div><div><br></div><div>It appears we are using a server-side script to p=
revent name clashes (since we are using windows clients) on our server in C=
ase 3. =C2=A0Why would Case 3 get caught (--parents) but Case 1 seem to sli=
p by this server side script and return a different error? =C2=A0I assume w=
e&#39;re using the stock=C2=A0case-insensitive.py, but regardless, I don=
9;t understand the behavior difference.</div>
<div><br></div><div>As I would expect, I cannot perform an &quot;svn info&q=
uot; on the incorrect-cased path. =C2=A0I was hoping I could do an &quot;sv=
n info&quot; to test/determine what the case corrected path is, but will ha=
ve to try an &quot;svn copy --parents&quot; first and if it fails due to a =
case clash, retry with the returned clash info. =C2=A0Is there a better way=
 to accomplish this? =C2=A0I do understand this is more of a corner use cas=
e, especially since Subversion is (properly IMO) designed around case sensi=
tivity. =C2=A0</div>
<div><br>Thanks,<br>Dan</div></div>

--f46d044288026fa80204f9dc0aa6--