Re: Newbie Problem: About repositiory
Xicheng Jia wrote: On Mon, 4 Nov 2002, Mike Ayers wrote: 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` Can you tell me how to make such script file? NOTE: this is extremely dangerous! *MAKE A BACKUP FIRST* find . -type f -name Root |xargs rm Also, shall I delete all 3 files in CVS directory or just the file Root? Thanks a lot. :-) Just delete the CVS/Root files. Wiping out any more will break the working directory. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
On Mon, 4 Nov 2002, Mike Ayers wrote: 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` Can you tell me how to make such script file? My working directory have too many subdirectories.. Also, shall I delete all 3 files in CVS directory or just the file Root? Thanks a lot. :-) Xicheng ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
How about: A. checkout new working dir using new repository location B. transfer content of old working copy to new working copy C. delete and cvs remove files from new working copy if necessary D. get rid of old working copy and continue work in new working copy Erik Mike Ayers [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 11/05/2002 12:31 AM To: Noel Yap [EMAIL PROTECTED] cc: Xicheng Jia [EMAIL PROTECTED], CVS [EMAIL PROTECTED] Subject:Re: Newbie Problem: About repositiory Noel Yap wrote: There're several things (with varying pro's and con's) you can do: 1. move back the repo until you've checked in everything you need (and don't checkout another working directory until it's moved back) 2. create a symlink (or mount the new repo) to the location of the old repo 3. modify all your CVS/R* files to point to the new repo 1 and 2 may not be possible in your environment. 3 is intrusive and error-prone. What about...? 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` Won't this do the trick? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
[EMAIL PROTECTED] wrote: A. checkout new working dir using new repository location B. transfer content of old working copy to new working copy C. delete and cvs remove files from new working copy if necessary D. get rid of old working copy and continue work in new working copy That is pretty fool-proof, but you lose existing intermediate build files, which may or may not be a big deal. Mike Ayers [EMAIL PROTECTED] 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` s/directories/files/ and this works. Nice tip! Much better than running N processes to delete/modify existing files... Also note that if $CVSROOT is defined to the new location, you can just 'cvs up'. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
Hello Mathew, re intermediate build files, I don't quite see why you'd have to lose them. Just copy them over. To clarify, what I meant by step B is a raw copy of every file in your old working dir to the new working dir. AFAICT the only thing you have to worry about are files that you got rid of in the old working directory and which show up in the new working directory. Probably those files were deleted and 'cvs remove'd but not yet committed. So that information will be lost, but that's just a matter of 'cvs remove'ing them again. The basic idea of a new checkout and a raw copy is actually a renewal of the CVS/Root files without bypassing cvs. That said, I agree that the other solution sounds better. Haven't had the chance to test it though I guess you've taken care of that. Erik Riechers, Matthew W [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 11/05/2002 03:25 PM To: [EMAIL PROTECTED] cc: Mike Ayers [EMAIL PROTECTED], CVS [EMAIL PROTECTED], i Xicheng Jia [EMAIL PROTECTED] Subject:Re: Newbie Problem: About repositiory [EMAIL PROTECTED] wrote: A. checkout new working dir using new repository location B. transfer content of old working copy to new working copy C. delete and cvs remove files from new working copy if necessary D. get rid of old working copy and continue work in new working copy That is pretty fool-proof, but you lose existing intermediate build files, which may or may not be a big deal. Mike Ayers [EMAIL PROTECTED] 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` s/directories/files/ and this works. Nice tip! Much better than running N processes to delete/modify existing files... Also note that if $CVSROOT is defined to the new location, you can just 'cvs up'. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
--- Riechers, Matthew W [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: A. checkout new working dir using new repository location B. transfer content of old working copy to new working copy C. delete and cvs remove files from new working copy if necessary D. get rid of old working copy and continue work in new working copy That is pretty fool-proof, but you lose existing intermediate build files, which may or may not be a big deal. This is extremely dangerous! You will lose the version that was originally checked out thereby possibly overwriting changes that have already been checked in. Noel __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
Xicheng Jia wrote:
I have several modules in my repository under the following
directory:
/users/t1/CVSROOT
But recently, our system administrator transfered all my data to another
directory, say:
/users/005/t3/CVSROOT
Then I can not checkin or do some other cvs operations correctly on
the files I checkouted out several weeks before, b/c the CVS root had been
changed.
The CVS/Root files in your sandbox(en) need to be updated to reflect the
new repository path. The following will generate a script to do the
conversion:
find . -type d -name CVS \
|awk '{print echo $CVSROOT \ $1 /Root\}'
You can tweak the output if need be, then just run the script from the
top of a sandbox. $CVSROOT needs to be set to the new location. Use at
your own risk!
-Matt
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
There're several things (with varying pro's and con's) you can do: 1. move back the repo until you've checked in everything you need (and don't checkout another working directory until it's moved back) 2. create a symlink (or mount the new repo) to the location of the old repo 3. modify all your CVS/R* files to point to the new repo 1 and 2 may not be possible in your environment. 3 is intrusive and error-prone. HTH, Noel --- Xicheng Jia [EMAIL PROTECTED] wrote: I have several modules in my repository under the following directory: /users/t1/CVSROOT But recently, our system administrator transfered all my data to another directory, say: /users/005/t3/CVSROOT Then I can not checkin or do some other cvs operations correctly on the files I checkouted out several weeks before, b/c the CVS root had been changed. Can anyone tell me what I should do to recover the relationship between my files and the modules. Also, shall I re-import the modules??? Thanks a lot for your kind help. Have a nice day, :) Xicheng ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
Xicheng Jia writes: Then I can not checkin or do some other cvs operations correctly on the files I checkouted out several weeks before, b/c the CVS root had been changed. Can anyone tell me what I should do to recover the relationship between my files and the modules. Also, shall I re-import the modules??? Thanks a lot for your kind help. CVS remembers the root for each working directory in the CVS/Root file -- you can edit those files as required. You can also use the -d global option to override what's in the CVS/Root files, but that's much less convenient for the long term. -Larry Jones Hey Doc, for 10 bucks I'll make sure you see those kids in the waiting room again real soon! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Newbie Problem: About repositiory
Noel Yap wrote: There're several things (with varying pro's and con's) you can do: 1. move back the repo until you've checked in everything you need (and don't checkout another working directory until it's moved back) 2. create a symlink (or mount the new repo) to the location of the old repo 3. modify all your CVS/R* files to point to the new repo 1 and 2 may not be possible in your environment. 3 is intrusive and error-prone. What about...? 4. Run a script which deletes all the CVS/Root directories and then `cvs -d /new/path/to/repository update` Won't this do the trick? /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
