SVN Interesting Behavior

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.

//SIGNED//

Matthew J. Krizo Civ.

Research Engineer

voice: (937) 255-3636 x7111 (DSN 785)

fax: (937) 656-6000 (DSN 986)

matthew.krizo@afit.edu