subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <b...@qqmail.nl>
Subject RE: SVN lock at version 1.8.3 and 1.8.4 - not working
Date Fri, 15 Nov 2013 19:12:49 GMT


> -----Original Message-----
> From: Kovar, Vaclav (EOM) [mailto:Vaclav.Kovar@skoda-auto.cz]
> Sent: vrijdag 15 november 2013 16:42
> To: users@subversion.apache.org
> Subject: SVN lock at version 1.8.3 and 1.8.4 - not working
> 
> We use Apache Subversion1.8.3 and i now tested new Apache Subversion
> 1.8.4 and got same result. When i checked out repo and tried to  get lock
on
> file,  i got result bellow:
> 
> C:\software\test\test6>c:\software\Subversion\bin\svn.exe lock --
> username iras24 test001/testfile.txt
> svn: E200035: sqlite[S19]: LOCK.lock_token may not be NULL
> svn: E200035: Additional errors:
> svn: E200035: sqlite[S19]: LOCK.lock_token may not be NULL
> 
> from error.log (apache had debug level set):
> 
> [Fri Nov 15 16:05:16.421641 2013] [authz_core:debug] [pid 9844:tid 1032]
> mod_authz_core.c(799): [client 127.0.0.1:53766] AH01626: authorization
> result of <RequireAny>: denied (no authenticated user yet)
> [Fri Nov 15 16:05:16.421641 2013] [authz_core:debug] [pid 9844:tid 1032]
> mod_authz_core.c(799): [client 127.0.0.1:53766] AH01626: authorization
> result of Require valid-user : granted
> [Fri Nov 15 16:05:16.421641 2013] [authz_core:debug] [pid 9844:tid 1032]
> mod_authz_core.c(799): [client 127.0.0.1:53766] AH01626: authorization
> result of <RequireAny>: granted
> [Fri Nov 15 16:05:16.421641 2013] [dav:error] [pid 9844:tid 1032] [client
> 127.0.0.1:53766] Tried to attach multiple locks to a resource.  [400,
#405]

What output does your 'pre-lock' hook template produce?

My guess would be that it produces something...

>From the standard template you get on 'svnadmin create':
#!/bin/sh

# PRE-LOCK HOOK
#
# The pre-lock hook is invoked before an exclusive lock is
# created.  Subversion runs this hook by invoking a program 
# (script, executable, binary, etc.) named 'pre-lock' (for which
# this file is a template), with the following ordered arguments:
#
#   [1] REPOS-PATH   (the path to this repository)
#   [2] PATH         (the path in the repository about to be locked)
#   [3] USER         (the user creating the lock)
#   [4] COMMENT      (the comment of the lock)
#   [5] STEAL-LOCK   (1 if the user is trying to steal the lock, else 0)
#
# If the hook program outputs anything on stdout, the output string will
# be used as the lock token for this lock operation.  If you choose to use
# this feature, you must guarantee the tokens generated are unique across
# the repository each time.

	Bert


Mime
View raw message