Migrating CVS database and users from NFS to pserver

We decided to convert our database from NFS to pserver, we hope our database corruption problems with the history will go away. What is the best way to migrate the users and the database? I can find documentation on creating databases, but not on migrating from NFS other methods. Have I missed

pseudo modules

Hi all, I have a need to allow certain projects using cvs to have access to (and modify in their own branches) previously defined modules 'as at' a certain point in time. Having had bad experiences with projects using specific tags or branches of modules and inadvertantly corrupting them (or s

Re: Migrating CVS database and users from NFS to pserver

[EMAIL PROTECTED] wrote: > > We decided to convert our database from NFS to pserver, we hope our > database corruption problems with the history will go away. > > What is the best way to migrate the users and the database? The "database" is just a directory. Are you moving the repository to ano

Re: Migrating CVS database and users from NFS to pserver

Matt Riechers wrote: > The "database" is just a directory. Are you moving the repository to > another location or machine? If so, you'll just have to move the tree by > hand, otherwise leave it alone. We haven't left it alone, we chown and chgrp the database to match the userid and group of t

CVS hangs on checkout of large project

I'm trying to use CVS to import a large pre-existing project -- the files are about 1 Gig -- and I'm having problems with the checkout. The import goes fine, but when I checkout, it hangs at one particular file. It seems to be the same one every time, but this file is unexceptional -- it's a 12k

Getting new directories on trunk-to-branch merge.

Hi, If I'm doing a merge, say, from trunk to branch, and new directories have been created on the trunk since the branch was made, is there a way to get those directories on the branch as well? I've tried "cvs up -d -j HEAD", but that didn't work; this implies to me that I have to re-add and

Re: CVS hangs on checkout of large project

[EMAIL PROTECTED] wrote: > > I'm trying to use CVS to import a large pre-existing project -- the files > are about 1 Gig -- and I'm having problems with the checkout. > > The import goes fine, but when I checkout, it hangs at one particular file. > It seems to be the same one every time, but thi

sh: - : unrecognized option...?!?!

Hi all, I keep getting this print out when committing and updating (WinCvs 1.2): - cvs -q commit -m "Blabla..." file.cpp (in c:\trash) RSC file: somefile.cpp,v done Checking in file.cpp; /var/cvs/... <--- file.cpp initial revision: 1.1 done sh: - : unrecognized option Usage:

Re: Migrating CVS database and users from NFS to pserver

[ On Thursday, August 1, 2002 at 10:02:59 (-0400), Martin d'Anjou wrote: ] > Subject: Migrating CVS database and users from NFS to pserver > > We decided to convert our database from NFS to pserver, we hope our > database corruption problems with the history will go away. Why don't you go all th

CVS tools to allow for code review / merge management

I'm looking to either use or write a tool that would allow us to achieve the following workflow with our CVS repository: - Developers write code and commit changes - Lead developer reviews the code changes, and either signs off on it or sends it back to the developer with comments - When lead d

RE: (no subject) - Thanks

Thanks a lot!!! [bot] I didn't have that syntax possibility (i also had read that info from the bsd man) so i thought it was a bit weird mine didnt accept it. Anyway all i needed was to compile a newer inetd to get that syntax possibility ;-) Cheers, -Josh -Original Message

Re: generating patches

ppotter wrote: >Hi. I am trying to generate a set of patches for a set of files. > >I retrieved the set of files from the sourceforge project and made >some modifications, which included adding completely new files. >When I tried to generate a patch listing with > >cvs diff -RN > >I got e

Re: sh: - : unrecognized option...?!?!

Tommy Svensson wrote: >Hi all, > >I keep getting this print out when committing and updating (WinCvs 1.2): > >- >cvs -q commit -m "Blabla..." file.cpp (in c:\trash) >RSC file: somefile.cpp,v >done >Checking in file.cpp; >/var/cvs/... <--- file.cpp >initial revision: 1.1 >done

Re: Getting new directories on trunk-to-branch merge.

James Hughes wrote: > Hi, > > If I'm doing a merge, say, from trunk to branch, and new directories > have been created on the trunk since the branch was made, is there a > way to get those directories on the branch as well? I've tried "cvs up > -d -j HEAD", but that didn't work; this implies t

modules file to include a sub-project?

Hi, I have a number of projects which all use a particular file (or directory of files). Is there a way to get a particular file to be shared amongst projects, ie by making the shared file/directory another project and using the modules file? (Ive looked in the modules file but cant quite work

Newbie Q: "cannot open CVS/Entries for reading"

Hi, I'm trying to make CVS work on our HP-UX 11.0 network. 1. Downloaded CVS and installed it. 2. Specified CVSROOT in .cshrc 3. Created a repository with "cvs init" 4. Checked in/committed a bunch of files with "cvs ci *.v" 5. I setup the .cshrc file for another user, Peggy. 6. Peggy tried to c

Re: Newbie Q: "cannot open CVS/Entries for reading"

H Albin Takami wrote: > 4. Checked in/committed a bunch of files with "cvs ci *.v" What are *.v files? (Just curious) > 5. I setup the .cshrc file for another user, Peggy. 5.5 When did Peggy do `cvs checkout project/module`? This is when the CVS directorie