Re: move cvs from solaris to solaris

[Todd Denniston]

Jim Hyslop wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> address@hidden wrote:
>
> > I have a couple of questions.
<SNIP>
> > Question4.  What else am I missing.
>
> Backups, before and after the move.
>
> You *must* make the old repository read-only before you start. Otherwise
> you run the risk of users checking in data to the old repository during
> the move, or some users checking in data to the old repository while
> others check in to the new repository. You can make it read-only by
> using o/s permissions, or (if you're using pserver) creating an file
> $CVSROOT/CVSROOT/writers (see section 2.10 of the link I provided
> above), or by using the cvs_acls script (it's in the contrib/ directory
> of the source code distribution).

The simplest thing would be setting commitinfo and taginfo DEFAULT entries to 
point to /bin/false and an empty CVSROOT/writers, while doing the backup.

Changing the OS's File System permissions has the bad effect of needing to 
remember and replicate the correct settings for all the directories when you 
untar on the new system, not fun. I realized this when I migrated a project 
between organizations, and had done it by providing them a CD-ROM made by 
simply `mkisofs /path/to/proj/repo`, i.e., all the directories were read only 
and owned by root when they copied them from the cd to their new dev machine, 
not at all what I intended to do to them.

I am beginning to think I have seen Jim and I answer this question a couple of 
times lately...perhaps it is almost time for one of us to break down and make 
a new FAQ entry on how to lock up a repo prior to making a backup for a move. 
nah...I'm too lazy right now:)
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter