Locking problem with the putfile.py from tools/examples
From: Sean McGrath <sean.mcgrath_at_propylon.com>
Date: Tue, 30 Dec 2008 15:02:28 -0800 (PST)
I am trying to get two standalone Python scripts together for locking and unlocking files in a repository. The idea is for these to work directly on the repository - not on a working copy. The are analogous to putfile.py from tools/examples in that respect.
Using Kevin Gillette's notes on  I have created a lockfile.py.
The problem is that once a file is locked, I can no longer use putfile.py to update the file using the same identity that holds the lock.
The exception thrown is svn.core.SubversionException: (
Kevin Gillette's notes on  speak about associating a username with the repos pointer like this:
access = fs.create_access(username)
Adding these to putfile.py before creating the transaction improves/changes matters. The exception changes to:
I'm guessing that the issue comes down to putfile.py having to provide a lock token as well as an identity (something that a working copy client would do automatically.)
Does this sound plausible? Is there a mechanism through the Python APIs for me to provide the lock token?
I have a self contained zip that illustrates the problem if anybody is interested.
Is this a bit low level for the users list? Should I move this to dev?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
This is an archived mail posted to the Subversion Users mailing list.