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

Re: still inconsistent, file in repository, but not in wc

From: solo turn <soloturn99_at_yahoo.com>
Date: 2002-08-21 14:14:43 CEST

hmmm ... i think i'm lacking some knowledge here:
the directory structure is (all in repository):
a/b/c/somefiles
a/b/d/somefiles

c is the problem directory i was talking about: in repository through
funny update with non-matching apr's. working copy does not have it.

i did:
$ cd a/b
$ svn status
? c
$ mv c c_sav
$ svn status
? c_sav
$ svn up
At revision 105.
$ cd ..
$ mv b b_sav
$ svn status
svn: No such file or directory
svn: assemble_status: b: No such file or directory
$ svn up
svn: No such file or directory
svn: svn_io_file_open: can't open `b/.svn/lock'

--- Ben Collins-Sussman <sussman@collab.net> wrote:
> solo turn <soloturn99@yahoo.com> writes:
>
> > how can i repair the following case:
> > - a file and a dir is in the repository
> > - the working copy knows nothing about it
> > but i could put the files there
> > (i got "?" as status, and with "add"
> > i got status "A" ... which clearly does
> > not help)
> >
> > preferable, without throwing away the whole working-copy and do a
> > "co" again.
> >
> > (after this ... we should be ok again ... and this caused by
> > inconsistent apr *sweat*).
>
> Don't delete the whole working copy. Delete the one directory that
> is
> "missing knowledge" of the file. Then 'svn up' the whole working
> copy. The client will report the directory as missing, and the
> server
> will resend the whole directory.
>
>

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 21 14:15:15 2002

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

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