[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Commit failure and KILLME file.

From: Martin Tomes <lists_at_tomes.org>
Date: 2004-04-23 11:31:00 CEST

Copied to the Subversion dev list as this is probably a core Subversion issue.

We just had a commit fail with a message saying that a directory was not locked. Actually, the
commit succeeded but the update of the working copy failed. When we tried an svn cleanup it refused
to clean up saying it couldn't open KILLME because it exists. Having removed that file and done a
cleanup and update we are left with a lot of binary files which are flagged as having a conflict
when it looks like they don't (the repository version does match the working copy file).

The directory which was not locked was inside another directory which was being deleted.

This is bad, and there is no obvious way to recover. Files which were added and changed are still
shown as being added/changed in the working copy even though they are in the repository. The only
option appears to be a new checkout and then a long laborious check to make sure all the changes did
get committed.

What is the best way out of this?

Is this a known problem or is a new Issue required?

Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
  | sed -e 's/ x /\./g' -e 's/ at /@/'
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 23 11:31:26 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.