We seem to have a deadlock of some kind... At the end of a system build we commit our built components to a binary repository...
svn cleanup --username xxxxx --password xxxxx svn commit -m "build msg" --username xxxxx --password xxxx svn: E155010: Pristine text 'd9b41b57756396b9cb236801fc02e0da0a83dffe' not present svn: E155004: Commit failed (details follow): svn: E155004: Working copy 'D:\xxxxxx\Base' locked. svn: E155004: 'D:\xxxxx\Base' is already locked. svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) If I run svn cleanup again I get: svn: E155010: Pristine text 'd9b41b57756396b9cb236801fc02e0da0a83dffe' not present or update: svn update svn: E155004: Working copy 'D:\xxxxxx\Base' locked. svn: E155004: 'D:\xxxxx\Base' is already locked. svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) The working copy is quite new i.e. not much opportunity to screw it up :( Simon Heffer Please consider the environment before printing this e-mail. Micro Focus Limited is registered in England and Wales. Registered number: 01504593 Registered office: The Lawn, 22-30 Old Bath Road Newbury, Berkshire, RG14 1QN, UK This message has been scanned by MailController - portal1.mailcontroller.co.uk
