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

Bug in cleanup?

From: Igor Fischer <fischer_at_informatik.uni-tuebingen.de>
Date: 2005-12-16 09:58:01 CET

I encountered something which I think is a bug: I was prompted to do
cleanup, but when I try it, I get the error message

   svn: In directory 'dvb-sim'
   svn: Can't copy
     dvb-sim\.svn\tmp\text-base\dvbt_3_convcode.m.svn-base' to
     'dvb-sim\dvbt_3_convcode.m.6.tmp': Das System kann die angegebene
     Datei nicht finden.

(the last sentence is in German, don't blame me for that)

So I cannot update, unlock, cleanup, or work in any way with the repository.

HOW DID THIS HAPPEN?

I work with Matlab on Windows. I had an opened file in my subversioned
directory (i.e. a Matlab program didn't close it, because it crashed)
and I tried 'svn update'. The 'update' wanted to delete the file, but it
couldn't, and reported a suitable error message ("Cannot remove a file
used by other process" or so).

O.K. So I close Matlab and try 'update' again. It says, "Working copy
locked, use 'cleanup'". Very well. But when I try cleanup, I got the
above error message and I'm stuck.

The directory "dvb-sim\.svn\tmp\text-base\" is empty, so it's clear that
the system cannot copy the file. But what should I do?

I mean, there is a simple workaround: delete the whole directory and
check it completely out again. But shouldn't there be a cleaner way?

Igor Fischer
http://www.nt.uni-saarland.de/people/fischer

(Please don't use the "From" or "Reply-To" address for replying, it
isn't valid any more and I use it only to confuse spammers. My valid
e-mail address is available from my home page)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 16 19:25:58 2005

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

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