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

Re: SVN 1.7 problems with case insensitive file systems (Windows)

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 12 Sep 2011 13:01:41 +0100

I don't think this is a problem with the command line processing
(although it may be a problem with my example, perhaps

# move foo foo_temp
# svn rm foo
# move foo_temp FOO
# svn add FOO
# svn ci

would work better).

However you achieve it, Marc's earlier mail showed the wc.db with a
deleted tree and an added tree with names that differ only in case:

sqlite> select local_relpath, op_depth, presence from nodes;
a|0|normal
a/b|0|normal
a/b/e|0|normal
a/b/e/alpha|0|normal
a/b/e/beta|0|normal
a/b/lambda|0|normal
a/d|0|normal
a/d/gamma|0|normal
a/mu|0|normal
iota|0|normal
|0|normal
a/b/E|3|normal
a/b/E/alpha|4|normal
a/b/E/beta|4|normal
a/b/e|3|base-deleted
a/b/e/alpha|3|base-deleted
a/b/e/beta|3|base-deleted

and the commit failed compaining the a/b/E is missing. Now that commit
works, on case-sensitive and case-insensitive filesystems, when the
added tree is a mv with copyfrom. Marc's mail appears to show that it
fails on Windows when the added tree is a plain add without copyfrom.

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2011-09-12 14:03:02 CEST

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