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

FAQ suggestion/question

From: Duncan Murdoch <subversion_at_murdoch-sutherland.com>
Date: 2004-08-20 15:29:21 CEST

The FAQ on http://subversion.tigris.org/project_faq.html talks about
the problem of changing the case of a filename when using Windows, in
the question

 I checked in a file but had the wrong case in the filename. How do I
change it?

I'd suggest that it also talk about how to fix things when someone
else changes the case of an existing file. Here's a recreation of
what happened to me recently, when someone on Unix changed readme to
README:

>$ svn update
>svn: Failed to add file 'README': object of the same name already exists

README clashes with readme, so I can't do the update. So, delete
readme...
>
>$ rm readme
>
>$ svn update
>Restored 'readme'
>svn: Failed to add file 'README': object of the same name already exists

It got restored before the update. So try renaming it:

>
>$ svn mv readme readme.old
>A readme.old
>D readme
>
>$ svn update
>A README
>D readme
>Updated to revision 149.

Good, things worked! Now delete the junk file, and things go wrong,
because it deletes the backup for README, which has overwritten the
one for readme:
>
>$ svn rm --force readme.old
>D readme.old
>
>$ svn update
>svn: Can't copy '.svn/text-base/README.svn-base' to '.svn/tmp/text-base/README.s
>vn-base.tmp': The system cannot find the file specified.

How should I have done this? It shouldn't be necessary for every
Windows user to do commits to the repository to update their checked
out version, and asking for a new checkout seems a little extreme....

Duncan Murdoch

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 20 15:29:37 2004

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.