2009/4/27 Gillis, Paul <pgillis_at_insight-tek.com>:
> We've experienced a similar issue with case sensitivity on commits. Every time I think I've got it figured out, the behavior defies my understanding. Maybe somebody can clarify it for me.
>
> I deliberately created all our repository names in upper case so that Windows users would not get confused about the first letter capitalization that Windows Explorer does by default. All of my svnaccessfile repository entries were defined in upper case as well. I did that so the svnaccessfile would match the folders.
>
> When I do a checkout, Tortoise lets me enter either upper case or lower case names. When I try to commit, the server then looks up the repository name in the svnaccessfile to see if I am allowed. But it does not seem to find upper case entries consistently. Some users who entered upper case repository names when they checked out have no problem committing. Other people get the 403 MKACTIVITY Error. If I change the case of the repository entries in the svnaccessfile to be lower case, the users who checked out and were able to commit successfully in lower case now get the 403 MKACTIVITY Error.
>
> I had thought that we figured out a rule of thumb when we first ran into this setting up our server. Always create folders in upper case and define them in the svnaccessfile in lower case. But that does not seem to work for everyone.
>
> Is there a definitive rule on how best to deal with this?
As this is a server question you will get more and better answers on
the subversion users list.
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1952066
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-27 23:14:52 CEST