svn commit still holds locks when server-side post-commit runs

I am using svn 1.4.4 (SUSE Linux 10.3) with a server-side post-commit
hook script that (under some circumstances) calls an svn update in the
same working directory in which I executed the svn commit. In that case,
I get an error message from the svn update, complaining that it cannot
acquire locks on the working directory.

Shouldn't "svn commit" have released all its locks on the working
directory by the time the post-commit script is executed on the server?

After all, the commit is over now, and all the "svn committ" command
still needs to do is to wait on any error messages that might still be
coming in from the post-commit script.

Or have the completion of the commit and the completion of the
post-commit hook script been lumped together into the same protocol
message?

Markus

-- 
Markus Kuhn, Computer Laboratory, University of Cambridge
http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org