RE: Re: Help - possible bug in Subversion!

Oh - dang, I feared that. Frankly I was hoping it was a user error on
my part! :)

The solution you give below is a bit painfull. The user that had this
problem had it occur near the root of a very large working directory (in
number of files and directory depth). Worse, yet he has quite a few
pending changes in his working directory.

I'm curious if there is another way to "clean up" in his case.

Is it safe to do the following:

1) rename the directory that was corrupted
2) do an "svn update" in the parent of the corrupted directory (which
would create a new (and fixed version of the corrupted directory)
3) replace the directories and files in the new directory with those
from the corrupted directory.

So in the end the only things that are new is the .svn of the corrupted
directory and the missing "Reports" subDir that was missing due to the
corruption.

I hope that made sense. Another way to ask this is:
1) Is the corruption only in the .svn directory of parent of the missing
subDir
2) Is it safe to move a sub-directory from one working directory to
another working directory derived from the same location in the
repository?

Ray

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Friday, June 04, 2004 2:16 PM
To: Ray Johnson
Cc: users@subversion.tigris.org
Subject: RE: Re: Help - possible bug in Subversion!

On Fri, 2004-06-04 at 16:03, Ray Johnson wrote:

> Perhaps it's as "svn update -N" became a sticky option - with no way
> to make it unsticky?!?!

Here's the bottom line. Don't ever use -N with checkout or update.
It's broken in a hundred ways, and described somewhat in issue 695. I
can't believe we released svn 1.0 with '-N' in the buggy state it's in.

I just reproduced your problem exactly:

$ rm -rf subdir
$ svn up -N
D subdir
$ svn up
[nothing]

...the subdir is gone forever, it's missing from the entries file, and
the entries file has *no* idea that it's got an incomplete list of
entries. It can't come back.

So here's what to do:

1. delete the directory in which you ran 'svn up -N'. it's a broken dir
now.

2. run 'svn up' in the parent dir to get it back (or, if you just
deleted the whole working copy, do a new checkout)

3. never ever touch -N again until we say it's safe. :-)

Ugh.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 4 23:42:12 2004