You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stefan Pettersson <st...@algonet.se> on 2004/05/29 16:07:53 UTC

RE: Win32 case-sensitivity problems (was: Custom Win32 binaries)

> Erik Huelsmann wrote:

> There to my knowledge two issues with case sensitivity. One 
> which constitutes a problem when two files with the same name 
> but different case exist in the repository; on case 
> insensitive systems this will bail out. 
> The other is one was recently fixed (as soon as the problem 
> was correctly diagnosed), where due to case insensitivity in 
> the filesystem local modifications could be overwritten.
> 
> The first problem is annoying but does not constitute 
> dataloss and does not prevent from work getting done. Also, 
> case sensitivity problems are not in the exclusive domain of Windows.

With the first problem, if you are referring to issue 1852 then, IMHO,
having developers in a team several times per week being forced to do a
complete checkout of >50k files to have a "non bailed out" working copy is,
IMHO, slighly more than annoying. During that hour it takes to restore the
working copy with all fiddling, it will most definitely "prevent work from
getting done".

(...some members of the team here at work have developed magical rituals
that they perform everytime they do a update/commit... They believe that by
doing that this issue is less likely to occur...)

- stefan


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Win32 case-sensitivity problems (was: Custom Win32 binaries)

Posted by Erik Huelsmann <e....@gmx.net>.
> 
> > Erik Huelsmann wrote:
> 
> > There to my knowledge two issues with case sensitivity. One 
> > which constitutes a problem when two files with the same name 
> > but different case exist in the repository; on case 
> > insensitive systems this will bail out. 
> > The other is one was recently fixed (as soon as the problem 
> > was correctly diagnosed), where due to case insensitivity in 
> > the filesystem local modifications could be overwritten.
> > 
> > The first problem is annoying but does not constitute 
> > dataloss and does not prevent from work getting done. Also, 
> > case sensitivity problems are not in the exclusive domain of Windows.

> With the first problem, if you are referring to issue 1852 then, IMHO,
> having developers in a team several times per week being forced to do a
> complete checkout of >50k files to have a "non bailed out" working copy
> is,
> IMHO, slighly more than annoying. During that hour it takes to restore the
> working copy with all fiddling, it will most definitely "prevent work from
> getting done".

Actually the second problem is described in issue 1854 and resolved in
release 1.0.4.  For the first problem I cannot find an issue, but I don't
expect there to be one either.  With the first problem, you have a situation
like this:

 /repos
   |-- A
   \-- a

under the repository there are two files with the same name differing only
in case.  When checking out a repository like that, svn will bail *always*
out with the 'object of the same name already exists' error.

Because of the description you give, I get a feeling you don't have a
situation like that, but do get (sometimes) the error mentioned.  Can you
describe the exact problem, investigate and describe the situation in which
this occurs?  It sounds like a situation which should not be occurring.


bye,


Erik.

-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org