Simon Heffer wrote on Fri, Aug 24, 2012 at 15:55:29 +0000: > > 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 >
Last I checked, 'cleanup' does not access the repository (well, maybe except for upgraded 1.0 working copies or something like that, Bert would know :)), so it doesn't need these arguments. > 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 :( > Great! Can you show a complete command sequence that starts with a clean checkout and ends with the above error? What's your svn --version? > > 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
