Joshua Wehner wrote:
> On Jan 11, 2005, at 10:33 AM, Max Bowsher wrote:
>
>>> At this point (this may not have been wise, I realize) I decided to
>>> copy over a back-up of the repository, made about a month ago.
>>>
>>> Now, when trying to interract with the database, I get this message:
>>>
>>> $ svn update
>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>> svn: Reference to non-existent revision '231' in filesystem
>>> '/Volumes/Data/svnrepo/db'
>>>
>>> What now?
>>
>> That last error is perfectly expected, since your working copy thinks
>> it is at a later revision than actually exists in the repository.
>>
>> Regarding recovering your problem repository:
>
> Ah. Well, you see, I have made this worse, then, I think. I completely
> failed to back up the broken repository. (One of those great,
> uncelebrated errors: Realizing just seconds after hitting "enter" that
> one really shouldn't have.)
>
> Um... am I sol, then? Can I do something to point my working copy at an
> earlier revision? Is that possible? Something with switch maybe? Is
> that insane?
You restored a month old backup, and tossed the current repository? Well,
thats a bit of an oops.
*MAKE A BACKUP OF YOUR WORKING COPY*, since it sounds like the only
remaining copy of your last month's work.
Your old working copy cannot talk to the repository now.
Check out a fresh old working copy, and recommit all the last month's
changes via the fresh working copy.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 11 19:29:53 2005