We have a subdirectory in our project called classes.
A lot of work was done by A and then the developer committed,
with some difficulty and error messages, he says. I don't know exactly
what he did to get his stuff up to the repository.
Later B wanted to update a long-dormant copy to pull all the new work.
The working directory at B now only has one file in the classes
subdirectory and it's supposed to have 8 or 9 important base classes for
the app to run, so naturally their working copy is badly broken.
The one at A is working, at least in the sense it has all the necessary
classes in its working directory and loads them.
The developer at B said she saw a "D classes" go by during the
update.
At either A or B, if you go into classes directory of the working copy
and do a "svn list" only the one file lists; however, all the class
files currently exist in the working copy at location A. If you attempt
to do a "svn add" at A of any of the files that seem to be missing from
the repository it says they are already under version control. If you
attempt to commit the individual files it just pops back with nothing.
If you attempt to update any of the individual files at location B
nothing happens. Bottom line: location A appears to have the only copy
of some of the new work and the repository doesn't and no one else can
get it
I'm sure I can fix this if A saves his current stuff, then everybody
reverts back a few versions and A just re-adds his stuff manually.
Is there an easier way to troubleshoot this issue? And how can I make
a best guess as to what back version we should all resynch on?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 23 17:12:43 2006