AW: SVN is ignoring needs-lock property
From: Markus Schaber <m.schaber_at_codesys.com>
Date: Tue, 29 Jul 2014 14:50:07 +0000
Hi,
Von: Niemann, Hartmut [mailto:hartmut.niemann_at_siemens.com]
The rule is: If the server (=repository) knows about a lock for that file, one can only commit with the matching lock token.
Working copies store the lock token when one locks a file there. However, this information can get out of sync, for example by:
- "stealing" a lock using "--force", the old working copy still has the stale lock token.
- Removing a lock on the server using svnadmin.
- Duplicating the working copy (e. G. using "copy" on the shell or zipping it together and unpacking on a different machine) - then the first one to commit or unlock has a valid token, while the other one does not have a valid token.
- Restoring an old working copy from a backup - the working copy may still have stale lock tokens for locks which were removed in the meantime.
(This list is non-exhaustive.)
Best regards
Markus Schaber
CODESYS® a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
E-Mail: m.schaber@codesys.com | Web: http://www.codesys.com | CODESYS store: http://store.codesys.com
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received
|
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.