2009/11/13 Jason Alexander <Jason.Alexander_at_ticketmaster.com>:
> 1. Using Tortoise SVN with the following versions:
> TortoiseSVN 1.6.6, Build 17493 - 32 Bit , 2009/10/19 20:22:18
> Subversion 1.6.6,
> apr 1.3.8
> apr-utils 1.3.9
> neon 0.28.6
> OpenSSL 0.9.8k 25 Mar 2009
> zlib 1.2.3
> 2. I attempted to checkout a module into a Windows environment. The module
> had files in the same directory that Windows would not allow due to case
> insensitive: SHA256.pod and sha256.pod.
> 3. This locked the checkout, resulting in the error seen below. I could not
> proceed with this module checkout until one of the 2 files was removed via a
> linux environment.
> The bug is that tortoise should be able to skip or at least provide a better
> error for this situaion.
Both the behaviour with case clashes and the error message come from
the Subversion library, not TortoiseSVN, so there is nothing we can do
to help here. It is a well known issue with subversion, which is case
sensitive, and it is not considered to be a bug. Having two files
whose names differ only in their uppercaseness is permitted on any
case-sensitive file system, and arbitrarily skipping one of them would
not be the right answer either.
However, I agree that the error message could certainly be a lot more
helpful, so do feel free to badger the subversion development team to
The only solution for the end user is to sort out the conflict and
remove or rename one of the files, if the directory is to work on both
Linux and Windows.
BTW you can do that from withing TortoiseSVN if you use the repo
browser to access the repository directly. That has no problems with
case sensitivity because the files don't have to exist on a Windows
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-16 00:26:28 CET