Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are using SubVersion to manage a big project, every one normally has to lock a file before to modify it, but on some new machine with Window 7 and SVN 64 bit also with this directive in the config file:

 ** = svn:needs-lock=true
 *.* = svn:needs-lock=true*

If a user with one of this new machine create a new file, this file will remain editable in every moment also without lock and without locking it and than causing a conflict.

How can I solve it?

share|improve this question

Eek. Merge, don't lock; this ain't CVS.

Likely the config file isn't actually being applied for whatever reason - where is this file located? You'll also need to make sure that enable-auto-props is set somewhere in the config.

To ensure that all your files have that property set regardless of client misconfiguration, add a pre-commit hook that rejects the commit if it's not present.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.