Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I recently upgraded my TortoiseSVN installation to version 1.7.1. This forced me to upgrade my working copy as well. The upgrade removed all (but one) of the .svn directories from all subdirectories leaving only one in the root.

Now out of the blue (of course; I suspect my antivirus software) there is an error when I for example try to clean up the working copy. I am also not able to commit anything.

The error message when cleaning up is:

Cleanup failed to process the following paths: C:\svn

Can't open file 'C:\svn.svn\pristine\73\73bcc5fa7819f84f56b81dfa0236f0aac7b7d404.svn-base': The system cannot find the file specified.

I traced the error to be related to the presence of one directory within the working copy. If I rename it then everything works. When it is present I get the error. I also deleted it and checked it out again. No change, the error persists.

With previous versions I could repair damages in the .svn easily: just delete the offending folder and check out again. I cannot do this anymore because now the .svn dir is centralized.

What could I do to repair my working copy?

share|improve this question
add comment

4 Answers

Can't open file 'C:\svn.svn\pristine\73\73bcc5fa7819f84f56b81dfa0236f0aac7b7d404.svn-base

I just had a similar error and I actually had to make that file with notepad and then cleanup worked.

share|improve this answer
add comment

We had the same problem after upgrading from older version to Tortoise SVN 1.7.7.

Since I found no other solution, I deleted the local working copy and checked it out again. It's working fine now.

share|improve this answer
add comment

I got the issue while I aborted a merge. I couldn't perform any SVN action. On doing an SVN cleanup it gave an error that it cannot find a specified file which lead to cleanup failure.

I created a dummy file with that exact name in the specified folder and did a SVN clean.

Then I was able to proceed.

share|improve this answer
add comment

I had a similar problem, where it was saying that a file C:\working_copy\dir\file.xml could not be found. I had deleted the dir directory. In my case, simply adding a new dir folder & file.xml file (with empty text) allowed the cleanup to continue, then I could properly re-update the working copy.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.