How do I resolve a Subversion "423 Locked" error?

Resolve this issue by removing all zombie locks from the repository, then remove the lock on the file or unlock the repository file.

Note: All solutions require access to the repository.

1. Remove all zombie locks from the repository.

svnadmin lslocks /var/svn/repositories/lockrepo-one/
Path: /trunk/file
UUID Token: opaquelocktoken:2001a3c5-151f-4ffb-95c4-cb965641dcc3
Owner: rparedes
Created: 2009-01-23 15:45:11 -0800 (Fri, 23 Jan 2009)
Expires:
Comment (0 lines):
# remove-zombie-locks.py /var/svn/repositories/lockrepo-one all
Removing all zombie locks from repository at /var/svn/repositories/lockrepo-one
This may take several minutes...
/trunk/file
Done.  

2. Unlock the repository file.

svnadmin lslocks /var/svn/repositories/lockrepo-two
Path: /trunk/file
UUID Token: opaquelocktoken:1486b5a8-89e2-4d54-bf66-906ff2fa0505
Owner: rparedes
Created: 2009-01-23 15:11:22 -0800 (Fri, 23 Jan 2009)
Expires:
Comment (0 lines):

svnadmin rmlocks /var/svn/repositories/lockrepo-two /trunk/file
Removed lock on '/trunk/file'.
$ svn status -u
A O 0 file
$ svn unlock file
svn: 'file' is not locked in this working copy
$ svn unlock --force http://cu119.cubit.sp.collab.net/svn/lockrepo-three/trunk/file
'file' unlocked.
$ svn ci -m ""
Adding trunk/file
Transmitting file data.
Committed revision 4.
Related information
Subversion - Locking