If you have deleted directory Dir-A/Dir-B/Deleted-Directory
then running svn cleanup will just make the state of the working copy
correct, i.e. it will just think you have a sparse checkout.
When you run update to the revision *after* the directory was deleted, it
will not even try to check it out.
What I suspect the problem is, is that it was not a directory that was
deleted, but the files in a directory... to fix such a working copy I just
delete the directory in question from my working copy (including the .svn
subdirectory)
svn cleanup
svn update
and away you go again.
-Stephen
2009/5/27 David Weintraub <qazwart_at_gmail.com>
> Okay. Let me get this straight: You had a Subversion working
> directory, and somewhere inside this working directory, you deleted a
> directory filled with very large files.
>
> I'm going to assume the structure looked like this:
>
> Dir-A/Dir-B/Dir-C
> Dir-A/Dir-B/Deleted-Directory
> Dir-A/Dir-B/Dir-D
> Dir-A/Dir-E
> Dir-F
> Dir-G
>
> Now, each Subversion subdirectory is a full Subversion working
> directory in it's own right. In the above, you could go into directory
> Dir-C, Dir-D, Dir-E, Dir-F, and Dir-G and run both "svn clenup" and
> "svn up". This would pretty much allow you to get much of your work
> area cleaned up.
>
> The problem is with Dir-A, and Dir-B since both of these have the
> deleted directory in their "working directory".
>
> What happens is when you do an update, Subversion puts a special lock
> file inside the .svn hidden directories that are under each and every
> directory inside Subversion. This is used to prevent duplicate
> "updates" from running.
>
> Unfortunately, I don't know what that lock file looks like, but this
> is what is preventing you from doing an update. I tried to crash an
> update process, so I can give you more information, but I couldn't get
> "svn up" to fail enough to create a situation where I had to do a
> cleanup.
>
> A "svn cleanup" is suppose to remove those locks.
>
> On the other hand, there comes a time when it is just easier to redo
> the entire checkout and forget about attempting to clean everything
> up.
>
> Anyway. try cleaning up and updating what you can, then maybe that
> will be enough to get the rest of your working directory unlocked and
> updateable.
>
> On Tue, May 26, 2009 at 6:17 PM, Julia Kamenetzky
> <julia.kamenetzky_at_colorado.edu> wrote:
> > I'm sorry I don't have a lot of background in what version I am using or
> > anything like that... if that information needs to be provided, please
> > inform me *how to find it*, thank you.
> >
> > I attempted to update my copy of our svn to revision 445, which contained
> a
> > lot of new, very large files. The update was interrupted because the
> disk
> > ran out of space. I informed my colleague that these files were huge and
> > asked if they could be kept somewhere other than the svn. They removed
> the
> > large files, and committed their copy, making it revision 446.
> >
> > I tried to update to this new revision, but received the message:
> >
> > svn: Working copy '.' locked
> > svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
> >
> > Okay, I understand that it was locked because the previous update was
> > interrupted and there is a log file telling it to try to finish the
> process
> > it started. Unfortunately, because I was completely out of disk space, I
> > removed some of the files that were added. So now when I try to cleanup,
> it
> > couldn't find the files and would not continue. I deleted the entire new
> > directory (with the big files), and so now i get;
> >
> > svn: 'foo' is not a working copy directory
> >
> > I can't add the directory back again because my working copy is locked.
> >
> > What I need to somehow do is get to revision 446 even though I was
> > interrupted in updating to r 445 and cannot complete the r 445 update
> (even
> > if I wouldn't have deleted the new directory, there wouldn't have been
> room
> > to complete the update). How can I do this?
> >
> > Thank you, again I would be happy to provide any other information if you
> > can tell me how to find it.
> >
> >
>
>
>
> --
> David Weintraub
> qazwart_at_gmail.com
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2355804
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2355832
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-27 18:57:39 CEST