I have been doing some testing with SVN 1.4.2 with Apache 2.2.3 and Neon
0.26.1 (I tried 0.26.2 as well), and cannot seem to get locking working.
I can lock and unlock files fine, but I get the errors when attempting
to commit, as shown in this excerpt from running lock_tests.py:
PASS: lock_tests.py 1: lock a file and verify that it's locked
subversion/libsvn_client/commit.c:865: (apr_err=160037)
svn: Commit failed (details follow):
subversion/libsvn_ra_dav/util.c:827: (apr_err=160037)
svn: MERGE request failed on '/svn-test-work/repositories/lock_tests-2/A'
subversion/libsvn_ra_dav/util.c:389: (apr_err=160037)
svn: Cannot verify lock on path '/A/mu'; no matching lock-token available
FAIL: lock_tests.py 2: commit a file and keep lock
subversion/libsvn_client/commit.c:865: (apr_err=160037)
svn: Commit failed (details follow):
subversion/libsvn_ra_dav/util.c:827: (apr_err=160037)
svn: MERGE request failed on '/svn-test-work/repositories/lock_tests-3/A'
subversion/libsvn_ra_dav/util.c:389: (apr_err=160037)
svn: Cannot verify lock on path '/A/mu'; no matching lock-token available
FAIL: lock_tests.py 3: commit a file and release lock
subversion/libsvn_client/commit.c:865: (apr_err=160037)
svn: Commit failed (details follow):
subversion/libsvn_ra_dav/util.c:827: (apr_err=160037)
svn: MERGE request failed on '/svn-test-work/repositories/lock_tests-4/A'
subversion/libsvn_ra_dav/util.c:389: (apr_err=160037)
svn: Cannot verify lock on path '/A/mu'; no matching lock-token available
FAIL: lock_tests.py 4: commit a locked file with a prop change
PASS: lock_tests.py 5: lock a file and verify lock breaking behavior
PASS: lock_tests.py 6: lock a file and verify lock stealing behavior
PASS: lock_tests.py 7: examine the fields of a lockfile for correctness
PASS: lock_tests.py 8: verify behavior when a lock in a wc is defunct
PASS: lock_tests.py 9: verify svn:needs-lock read-only behavior
PASS: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
When looking at the apache error log, it shows the following:
[Tue Nov 21 16:09:13 2006] [error] [client 10.45.214.219] Could not
MERGE resource
"/svn-test-work/repositories/lock_tests-2/!svn/act/626333ce-b67c-4070-b9c2-aad4a1678cb4"
into "/svn-test-work/repositories/lock_tests-2/A". [409, #0]
[Tue Nov 21 16:09:13 2006] [error] [client 10.45.214.219] An error
occurred while committing the transaction. [409, #160037]
[Tue Nov 21 16:09:13 2006] [error] [client 10.45.214.219] Cannot verify
lock on path '/A/mu'; no matching lock-token available [409, #160037]
These results are with the basic apache configuration given in the
README for this directory. I am using a somewhat stripped down apache
configuration (for directives which I thought would be unrelated to
SVN). Is there another apache configuration setting that could be
causing these errors? Any other ideas on possible causes of the error?
Thanks,
Brian
$ svn --version
svn, version 1.4.2 (r22196)
compiled Nov 21 2006, 15:48:52
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet
(http://www.Collab.Net/).
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
OS: RedHat Enterprise Linux 4 Update 4 (x86_64)
Apache 2.2.3
Neon 0.26.1
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 22 01:20:36 2006