svn resuming aborted checkout

Question

Situation - have enormous repository, slow and unreliable link (read - vpn that breaks from time to time).

We are subject of frequent branching, moving things, so ev

Answer 1

From the Subversion documentation

If you interrupt a checkout (or something else interrupts your checkout, such as loss of connectivity, etc.), you can restart it either by issuing the identical checkout command again or by updating the incomplete working copy.

Answer 2

move into the copy directory

svn update    
svn cleanup
cd..

svn checkout download_path

Answer 3

I also had same issue and finally thing which work for me is:- Step 1. In root folder right click on empty space and select "TortoiseSVN > Clean up..." then check all option in pop-up and run this Step 2. right click on empty space and click "SVN Update.."

It starts to resume now.

Answer 4

svn update

does the job for you.

Answer 5

Just ran into the same problem. I had to interrupt a checkout because it was taking an absurdly long time. When I went to "resume" the checkout, it wasn't clear whether I should re-initiate the checkout or simply do an svn update.

After attempting to to do the svn update to resume the checkout, I got a wonderful error message saying that the directory was "locked". I tried issuing a "Release Lock" from Tortoise SVN, but this didn't help.

Ultimately, what I ended up having to do was issue an svn cleanup to release whatever stranglehold Subversion had in place. After that, I was able to continue my previously initiated checkout by performing kicking off another update (svn update or "SVN Update" from the Tortoise SVN context menu).

Answer 6

The way I see it, there are three possibilities:

• It does the checkout correctly and completely, without any headache for you. Problem solved.

• It checks out everything that didn't get checked out last time. You do 'svn update' and you're golden.

• It discovers that some stuff has been modified since having been checked out, complains, and aborts. You'll just have to remove the conflicting stuff.

In any event, any file that's been successfully checked out of the repository has associated metadata in your local tree and that will ensure that 'svn update' will get you the most recent version.