[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Respository crashed, sandbox is from old Repository BUT is more cur
Derek R. Price
Re: Respository crashed, sandbox is from old Repository BUT is more current than restored CVS
Wed, 14 Feb 2001 10:39:48 -0500
The easiest way to do this is a fresh checkout and copying everything that
_isn't_ in a CVS directory from the old workspace. Then let CVS do the work of
determining what has changed and what hasn't as usual.
I've actually been known to handle this by copying all the CVS directories from
the freshly checked out workspace into the old one and performing a checkin in
the old one since it's easier to write the find command, but if you're going to
do this, be absolutely sure you've backed up your old workspace first. This
means working on the backup!
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden OpenAvenue ( http://OpenAvenue.com )
"I tried to think but nothing happened!"
Laine Stump wrote:
> "TC" <address@hidden> writes:
> > in line
> > >> So the CVS repository box died, restored backup to a new box but it
> > >> is about 2 days old, but THEY changed the repository name/server/ &
> > >> logins.. I want to sync up again,
> So you're saying that your backup is two days old, and there are
> changes you had updated to your local directory that aren't in the
> restored repository? In that case, you have two sets of valuable info in your
> workdirectory, and they key to it *all* is in your existing CVS/Entries files:
> 1) Files for which your CVS/Entries shows a newer revision than what
> is in the restored repository - your workdir contains a revision of
> that file that was lost when you lost your old machine.
> You should rite a script to shuffle through and find all these
> files, (or maybe even cvs -n update will report it to you as an
> error), and either commit the files you have (if you're 100%
> certain you didn't have any local mods to that file), or merge in
> the changes by hand. Do all this work in a newly checked-out work
> 2) Files for which your CVS/Entries file shows a revision that *does*
> exist in the repository, but "cvs -n update" shows that the file
> has been locally modified. In this case, you can just do a "cvs update"
> and continue working as if nothing had happened.
> Note that you should not perform *ANY* cvs operations on your old work
> directory without also giving "-n" on the commandline (eg "cvs -n
> update") until after you've taken care of step 1. After that, if you
> still receive any errors, you may need to tweak a few rev numbers in
> your Entries files by hand (if more than one revision was lost).
> Do not *at any cost* destroy your existing CVS/Entries by copying over
> the Entries file from a different workdir!!!