[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 'svn: Can't copy' when cheking out filenames with spaces

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-10 15:12:10 CEST

On Aug 10, 2006, at 01:42, cleber wrote:

> I'm using Subversion 1.3 on MacOSX 10.4.7 to check out files from
> my server, which is running Subversion 1.3.2 on Linux (Red Hat 9).

> When I tried to check out the project with the command:
> $ svn co -r 2 svn+ssh://svn@
> I got the following error :
> svn: Can't copy 'trunk/.svn/tmp/text-base/Relatorio de
> processos.txt.svn-base' to 'trunk/Relatorio de processos.txt.tmp':
> No such file or directory
> I guess it has something to do with the shell trying to interpret
> the spaces on the filename.
> I tried to checkout the project on a Windows NT box and got the
> same error.

No, there's definitely no problem with filenames with spaces. I just
confirmed that this works fine on Mac OS X 10.4.7.

Are you perhaps instead having a case collision? Although a
Subversion repository is case-insensitive and has no trouble storing
a file called "Relatorio de processos.txt" and a file called
"relatorio de processos.txt" in the same directory, both Windows and
Mac OS X by default use case-insensitive filesystems and cannot
handle that situation. Use "svn ls" on the repository URL to the
relevant directory to see if this is the problem in your case. If so,
the solution, as you discovered, is to rename one, or delete one, in
case they're duplicates of one another.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 10 15:13:59 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.