I figure at the minimum, the windows client should notice during
checkout and inform the user of the actual problem. The error that I
received, was a file not found error. It could simply print out that
there is an incompatibility between file systems and that it is unable
to checkout or update that particular directory.
Of course preventing this situation could be solved by having a
server side property set that would allow or disallow case insensitive
filename matches. I for one would rather this be turned on by default
given the user base of windowsXP clients. I would think that the
majority of subversion clients are unfortunately windows based and thus
should dictate the default. But at the minimum a property would be very
useful.
Sometimes commit hooks aren't all that great because of the amount
of information returned to a user. Some users, that are not familiar
with subversion can have trouble distinguishing between a subversion
error and a "business" error. I wish there was a basic text formatting
language or a cleaner return message to generic clients.
Anyways, thanks for the help!
Brad
On Tue, 2005-06-07 at 14:23 -0400, Scott Palmer wrote:
>
>
> On Jun 7, 2005, at 1:53 PM, Brad wrote:
>
>
>
> > I have encountered a severe problem with subversion in windowsXP.
> >
> > I believe a user copied over a file called temp.JPG that they wanted
> > to add to subversion, however another file, temp.jpg already
> > existed. Windows overwrote the old one, subversion thought it was a
> > new file and allowed the user to add it. Once the file was
> > committed,
> >
> > It appears that users can commit files with the same names in
> > different "cases". Linux handles this just fine, but windowsXP does
> > not. Currently any user that tries to checkout from the repository
> > in windows will get an error and cannot proceed. Even once I fix
> > this, around 2 dozen revisions will already be "un-checkout-able"
> > for them.
> >
> > Shouldn't subversion have the ability to prevent this?
> >
>
>
>
> Yes, it should.
>
>
> > Does it already?
> >
>
>
>
> No, it doesn't - at least not out of the box.
>
>
> > Do I need to create a hook?
> >
>
>
>
> Yes.
>
>
> > I need a way to prevent hundreds of users from doing this, many of
> > which are not computer literate. Any ideas?
> >
>
>
>
> Use a pre-commit hook that rejects commits that will result in files
> in the repository that only differ by case.
>
>
>
>
>
> Scott
Received on Tue Jun 7 20:42:06 2005