Need Information.
Hi, We are using PVCS version control system at present. We are planning to use CVS .Is it possible to import our repository from PVCS to CVS.If so can we keep same history of repository? Thanks Regards, Eswar ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: loosing branch when updating to a tag on the branch
This brings up a question I've had for quite a while: is there a way to close a branch? The only thing I can think of offhand would be to mark the tip of the branch as dead, by using 'cvs remove'. It won't prevent anyone from resurrecting the branch, though. It defeats version control, but can't you remove all versions on the branch and then remove the branch tag itself? That is of course only if the branch was just for some work and the work is now in the trunk. bye Fabi ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Need Information.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eswar [EMAIL PROTECTED] writes: We are using PVCS version control system at present. We are planning to use CVS .Is it possible to import our repository from PVCS to CVS.If so can we keep same history of repository? Thanks Regards, Eswar All version of cvs-1.11.x (starting with cvs-1.11.2 I believe and culminating in the cvs-1.11.17 and cvs-1.12.9 releases) come with a contrib/pcvs2cvs perl script. I have never used it myself. It is primarily intended to convert a VCS (or vcs) tree into a set of RCS archives. Converting from an RCS archive to a CVS repository is simple... just copy the ,v files into the repository in the hierarchy you desire. Good luck, -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBBK7J3x41pRYZE/gRAhp5AKDPnIV+qJHxXwyCquwsUnLlAgMGSACgpQMz 4paxVap7jGijzjKR/vVV0yM= =nIg6 -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
mutile root doesn't work ?
i put a new --allow-root option in the xinet, but the last path refused to work while server rejected access to the path for the user ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: loosing branch when updating to a tag on the branch
Right - I don't want to destroy the history, I just want to prevent future work from being performed on that branch. More to prevent accidental updates to it than anything else. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Cenedese Sent: Monday, July 26, 2004 3:08 AM To: [EMAIL PROTECTED] Subject: RE: loosing branch when updating to a tag on the branch This brings up a question I've had for quite a while: is there a way to close a branch? The only thing I can think of offhand would be to mark the tip of the branch as dead, by using 'cvs remove'. It won't prevent anyone from resurrecting the branch, though. It defeats version control, but can't you remove all versions on the branch and then remove the branch tag itself? That is of course only if the branch was just for some work and the work is now in the trunk. bye Fabi ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
dealing with exe-s in CVS
I need only one excutable to be in the repository for various reasons. CVS ignores all exe-s by default, but I can specify the cancellation of all default ignores during import. Is there any way I can ignore all the executables except this one I want? Thanks Khyati___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Problem of accessing branch
Winnie Du wrote: According to CVS manual chapter 5 (https://www.cvshome.org/docs/manual/cvs-1.12.8/cvs_5.html#SEC54), I created a branch named Maintenance to keep our production code for bug fixing and maintenance purpose. But other developers cannot see this branch, I mean they cannot access this branch. What happens whey they try to check out the branch? What error message, if any, do they get? Can you access the branch OK? Can the other developers access the trunk revisions OK? CVS Server is on AIX box, and we use WSAD (WebSphere Application Developer) as CVS client. All the users (including myself) belong to the same group. Can you try to reproduce the problem using the command-line client? -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Update problems - Can't parse date/time
[EMAIL PROTECTED] wrote: I am having trouble updating a source repository from our local testbed machine. [...] testbed53 [33] % cvs update . cvs [update aborted]: Can't parse date/time: . Don't specify '.' If you want only the current directory, use the -l option: cvs update -l If you want recursion (the default) just type 'cvs update' -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Need Information.
Eswar wrote: We are using PVCS version control system at present. We are planning to use CVS .Is it possible to import our repository from PVCS to CVS.If so can we keep same history of repository? Well, a quick search at Yahoo on convert pvcs to cvs turns up over 1,000 hits - there might be some useful information in one of those pages. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: dealing with exe-s in CVS
Khyati Nayak wrote: I need only one excutable to be in the repository for various reasons. CVS ignores all exe-s by default, but I can specify the cancellation of all default ignores during import. Is there any way I can ignore all the executables except this one I want? You could try using 'cvs add filename.exe' instead of 'cvs import'. Explicitly naming a file in 'add' will override any ignore rules. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: mutile root doesn't work ?
scsoce writes: i put a new --allow-root option in the xinet, but the last path refused to work while server rejected access to the path for the user You need to tell xinetd to re-read it's configuration. See the xinetd man page or your system administrator. -Larry Jones Hmm... That might not be politic. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Access to old historic CVS releases ?
[EMAIL PROTECTED] (Larry Jones) writes:
And as far as I understand the CVS archives of CVS itself aren't
available either.
They are. You can browse them on-line at cvshome.org by picking the
Version control link, or you can register as a user and then set up an
SSH tunnel for direct access as described in the CVS client setup
instructions on that page.
Sorry to butt in here... I'm a registered member and accessing the
above info at https://ccvs.cvshome.org/servlets/ProjectSource
In these steps which are links:
you must be a member of this project with the appropriate permissions, and
you must first set up an SSH tunnel for security purposes.
Download the [EMAIL PROTECTED] private key
Configure your SSH to use it
The link at:
you must first set up an SSH tunnel for security purposes
Seems to be broken... it leads to:
HTTP Status 404 - /servlets/{0}
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Access to old historic CVS releases ?
Harry Putnam writes:
The link at:
you must first set up an SSH tunnel for security purposes
Seems to be broken... it leads to:
HTTP Status 404 - /servlets/{0}
See the More about SSH tunneling link at the bottom of the page
instead.
-Larry Jones
Mom must've put my cape in the wrong drawer. -- Calvin
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
RE: loosing branch when updating to a tag on the branch
How about using the cvs_acls script? This is very effective for me (Thanks a lot to the person who wrote it) in controlling access. I believe this is in the contrib section. -Cheers, Yamuna -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Monday, July 26, 2004 8:58 AM To: [EMAIL PROTECTED] Subject: Info-cvs Digest, Vol 20, Issue 45 Message: 3 Date: Mon, 26 Jul 2004 09:07:56 +0200 From: Fabian Cenedese [EMAIL PROTECTED] Subject: RE: loosing branch when updating to a tag on the branch To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii This brings up a question I've had for quite a while: is there a way to close a branch? The only thing I can think of offhand would be to mark the tip of the branch as dead, by using 'cvs remove'. It won't prevent anyone from resurrecting the branch, though. It defeats version control, but can't you remove all versions on the branch and then remove the branch tag itself? That is of course only if the branch was just for some work and the work is now in the trunk. bye Fabi ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Any 'contrib' scripts have access to pre-commit source?
I would like to restrict certain types of changes to specific files in the repository. I'm using pserver access. In order to do this I need access to the source that is going to be committed. So, I was planning to write a script that would: 1) examine the pre-commit source 2) return a non-zero return code that would prohibit the commit commit_prep seems to be the ideal place to trigger such a script, but there doesn't appear to be any parameters in the commitinfo file that would forward the pre-commit source to the script. Any help would be appreciated. Thanks, pc ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Any 'contrib' scripts have access to pre-commit source?
At 06:12 PM 7/26/2004, Peter Connolly wrote: In order to do this I need access to the source that is going to be committed. I think that the default directory of the commitinfo script is the tmp directory that contains all of the files being committed. Try an experiment with a script that just grep's for some pattern in the list of files being committed. If you see the output of grep, then that's the right place. Take it from there Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Problem with omitting CVSROOT
Hi! I have some trouble working with my remote repository. I use pserver with ssh tunnel which works in general, but please take a look: [note: localhost:12401 is tunneled to 2401 on remote machine] $ export CVSROOT=:pserver:[EMAIL PROTECTED]:12401/var/cvs/ $ cvs login Logging in to :pserver:[EMAIL PROTECTED]:12401/var/cvs/ CVS password: $ cvs co anymodule cvs server: Updating anymodule [...] $ cd anymodule $ cvs log /var/cvs: no such repository $ cvs -d $CVSROOT log [desired output] $ cat CVS/Root :pserver:[EMAIL PROTECTED]:12401/var/cvs/ Okay, explicitly adding -d $CVSROOT makes things work, but that's not a satisfying solution. I would be very thankful for any suggestion/help, regards /daniel ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Problem changing Sticky Options
In my cvswrappers file, I have the line: *.rc -m 'COPY' It does not specify the -k option. I just got a complaint that all our .rc files had: Sticky Options: -kb I don't see how this happened (I am the only person who messes with keyword Substitution and other cvs team environment stuff) unless keyword substitution is tied to copy/merge in some form. We want keyword substitution in these files so I tried (in each directory): cvs admin -kkv VersionInfo.rc I got back: RCS file: /snip long path/VersionInfo.rc,v Done Accroding to cvs status, I still have a sticky option of -kb. We are running cvs server 1.11.5 on a sun and cvs 1.11.16 client under XP. I use command line cvs (although others use TortoiseCVS or WinCVS as a front end.) I haven't had any complaints about it. Any advice as to what I am doing wrong? Feel free to cite the docs if you know what I missed. I haven't posted it to the cvsnt group yet because I feel it is a problem in my method rather than with software. Liza Blaney Intel Corp, Intel Capital Group, DTO 2200 Mission College Blvd, Santa Clara CA 95052-8121 Mail Stop: RNB-4-97 Phone: 408-765-4495 ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
multiple password entries
Hello all, A quick question, I am using cvs over a network using rsh. When I release a project I get asked for my password for each file in the project. Is there a way to make cvs only ask once for each 'release'? Specs cvs 1.11p1 debian 3 PII 96mb ram the computer boxes are white. Cheers Mike ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Problem changing Sticky Options
Blaney, Liza writes: Accroding to cvs status, I still have a sticky option of -kb. Your cvs admin only affected the default keyword substitution mode in the repository files, it didn't affect the actual keyword substitution mode in your working directory -- you need to run update -A in the working directory to reset it. -Larry Jones Physical education is what you learn from having your face in someone's armpit right before lunch. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
