Hi guys, I've been trying to create a simple pair of hooks that sends out an email when someone locks or unlocks a file, and stumbled upon what seems to be a nasty bug. If I use a pre-lock script, the lock operation will execute (seemingly) successfully, the mail goes out, and all seems well. But 100% of the time, trying to release that lock will result in this error:
The locktoken specified in the "Lock-Token:" header did not specify one of this resource's locktoken(s). [400, #0] Googling this error led me to this old thread<http://groups.google.com/group/visualsvn/browse_thread/thread/5df31fce2313f379?fwc=1>, so I used svnadmin to remove the lock and tried it again and again, using several different combinations, but each time, the pattern was clear: - Using a pre-lock hook would guarantee the error always occurred on attempted unlock - It doesn't seem to matter if I used a pre-unlock hook or not, if the lock hook was a pre-hook it will cause the unlock to fail. - Removing the pre-lock hook, using svnadmin to nuke the lock and trying again would allow the lock and unlock to succeed. I am running VisualSVN server 2.15 on Windows Server 2008/x64 and the script I'm calling is a simple, one line batch file that calls a mailer app (bmail.exe). Client is TortoiseSVN 1.6.12. Thanks in advance anyone can provide regarding this issue. Dan Magaha PS, the only reason I'm using pre-lock/pre-unlock hooks is because I can get the full path of the file to be locked/unlocked from the "pre-" scripts (whereas the post scripts offer me only the somewhat useless repository path and username). Is there a more complete set of variables I can use in a post-lock and post-unlock hook? -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/visualsvn?hl=en.
