On 8/14/07, Krizo Matthew J AFIT/ENP <Matthew.Krizo@afit.edu> wrote:
>
>
>
>
> I observed some interesting behavior this past week while using SVN. I will
> state that although what our development group did was not planned and not
> recommended it still seems to be problematic. Here are the details.
>
>
>
> For revision 284 a file "plotOnWorldMap.m" was added to the repository
>
> For revision 286 a file "PlotOnWorldMap.m" was added to the repository
> (note capitalization difference)
>
>
>
> Upon checking out a new copy it would fail because it failed to add
> "PlotOnWorldMap.m" because it already existed. Of course only
> "plotOnWorldMap.m" existed. There seems to be some sort of odd behavior
> with SVN being only partially case sensitive.
>
>
>
> I was able to develop a workaround to get the repository back on track.
>
>
>
> For a workaround:
>
> Update to revision 285 (Immediately before problem file was introduced)
>
> Svn delete "plotOnWorldMap.m"
>
> Svn update (It is now able to update to the head revision)
>
> Svn delete "PlotOnWorldMap.m"
>
> Svn commit –m "Removed troublesome files"
>
> Add back the files with names that will not cause trouble.
>
>
>
> I hope this error report has sufficient detail to allow you understand this
> issue. Since my workaround has corrected the issue it is a low priority
> issue. Also it only shows up when you do not adhere to naming conventions
> and commit without updating first. In short this problem only occurred out
> of our failure to communicate internally, but I believe that this should be
> an easy modification to SVN and that it inclusion would yield a more robust
> product.
First, you're in the wrong place if you're asking for changes to the
Subversion "product." TSVN is just a client which builds upon the
Subversion libraries.
Subversion is completely case-sensitive. Problems arise when you have
working copies on filesystems which are not case-sensitive, such as
NFTS, FAT and HFS (by default; I understand there is a way to create
an HFS+ partition w/ case sensitivity).
When you check out a working copy to a case-insensitive filesystem and
there are 2 filenames in the repository differing only in case, you
will get an error because the WC's filesystem thinks the file already
exists. This is not a bug; it's really a conflict between a
case-sensitive tool and a case-insensitive filesystem, and it's
documented & expected behavior. Subversion isn't going to change to be
case-insensitive (people have asked on the SVN mailing list).
You could have simply renamed one of the files via repository URLs or
the repo-browser; you didn't need to do a delete.
Seriously consider installing check-insensitive.py from
http://subversion.tigris.org/tools_contrib.html#hook_scripts . It will
stop you from committing files with the same name, differing in case.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Aug 14 16:45:44 2007