URL case insensitivity vs SVN case sensitivity

Hello,

One of our developers stumbled across an interesting issue where he
capitalised the repository name for a checkout when he shouldn't have.

Both the Subversion command line tool and TortoiseSVN perform the
checkout, and both failed on the commit. It's worth noting that you can
only supply incorrect case on the server and repository name in the URL,
you can't supply incorrect case in the repository path.

Using svn 1.3.1, the error returned was:
svn: Commit failed (details follow):
svn: Authorization failed

Using TortoiseSVN 1.3.3, there was no error message other than:
Error Commit failed (details follow):

I'm assuming the issue is a conflict due to the URL being case
insensitive, as per RFC 1738, and Subversion being case sensitive.

The developer was able to fix the problem by performing a relocate,
a switch was insufficient.

Would (or should) it be possible to provide a warning when performing
a check out when there is a case conflict? Similar to the warning the
svn command line client gives when you add a path which already
exists with a different case.

Or should it have been possible for the developer to commit?
(After all, it let him checkout)

We're using Subversion 1.3.1 accessed via ra_svn with authorization
enabled.

peace
si

p.s happy to file as an issue if the hive mind deems it useful.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 16 05:13:32 2006