Re: Locking CVS
S I wrote: Hi everyone, I'm planning to lock cvs today getting ready for our release. I realize with certain version control software nowadays you don't have to lock the repo and the developers can continue with their work. However, we're imposing and enforcing a few days for freeze and to regroup. Our repository resides on a linux box with :pserver method access from WinXP CVS DOS and Tortoise clients. Could I just lock the repo by executing cvs admin -l or -L or do I have to download some perl module to accomplish this? I need to lock our CVS repository today. Three projects reside in the repository, is it possible to lock them selectively or would admin -l lock the entire repo? If you want to lock all projects, then create an empty $CVSROOT/CVSROOT/writers file. I believe this will work for all access methods, not just pserver. Unlocking the repository is a simple matter of deleting the file. See https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC36 for details. To selectively lock projects, have a look at the cvs_acls script. It's in the source code distribution (available from www.cvshome.org) in the contrib/ directory. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How can I administratively freeze a branch?
[EMAIL PROTECTED] wrote: Why not just cvs rm all the files from it, so they no longer exist at the head of the branch? People would have to accidentally checkout old revisions before they could accidentally commit to it; that's pretty improbable I think. The problem is that files from old branch still exist in HEAD (in fact, what we did was to commit the branched files to HEAD). I don't understand your objection. 'cvs remove' on a branch will declare the tip of the branch dead, thereby preventing anyone from checking anything into the branch. It's exactly what you want to do. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
Liquidchild wrote: I posted on here recently with regards to using SSH and SmartCvs, I have (i think) made a little head way in this but when trying to get the modules to read from smartCVS checkout project option i am getting the following: An i/o error occured, details: Unknown Compression method Turn off compression. There should be a checkbox on the check-in dialog for compression. There are known issues with compression on some versions of the CVS server. p.s. would have posted this on the smartCVS form but my company firewall blocks it! subscribe via email. Send an email to [EMAIL PROTECTED] Messages to the group can be sent to [EMAIL PROTECTED] once you're subscribed. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Undesirable Watch/Edit Behavior
[EMAIL PROTECTED] wrote: I've set up a CVS module with cvs watch on so that users have to use cvs edit to reserve files for editing. This works fine for serial editing of unmergeable binary files files. When users try to edit files already marked for editing by someone else they are told the file is unavailable for editing as expected. The problem that I've encountered is that if a user subsequently checks out the same module again to a different location (i.e. two different sandboxes for the same module) CVS forgets about any files that user marked for editing before the second checkout. Is this behavior by design or a bug? I'm using CVS version 1.11.1p1 on a Linux server? That's pretty much by design. Each checkout is completely independent of any other checkouts, and CVS does not make any attempt to coordinate between multiple checkouts. Thus, CVS has not forgotten anything - if your users go back to the first directory, they'll find that it is currently Edited by them. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: migration of CVS repositery from one machine to another
ravish agarwal wrote: Does that mean that by only copying the files of the repositery after installing the new version of CVS will do the needful. all the history-details will remain there.? also Is there any possilble version upgrade related issues. Please Help me out. As Todd Dennison wrote earlier in the thread, this is covered in the manual. Yes, that's all you need to do. There should be no other version upgrade issues. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Undesirable Watch/Edit Behavior
Todd Foster wrote: I am not sure I agree with that. The act of doing a fresh checkout of that file (either via a new checkout or update -C or what-not) makes CVS forget that you are editing that file. cvs editors no longer returns you as an editor of that file (regardless of where you run it from - either the first or the second directory). Personally, I consider that a bug. I believe I have even seen a patch submitted to change this behavior thought I don't remember what the patch did. Yes, I'd forgotten about that bug and patch - thanks for the reminder. I just checked the NEWS file, and it doesn't look like the patch has been released yet. My apologies for the misinformation. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How to control the current version of CVSROOT/modules ?
[EMAIL PROTECTED] wrote: Hi. Is it possible to roll back the version of the currently used CVSROOT/modules file? Say that a product rev. A is built using Ampersand modules. Say that the product is updated to rev. B, and that the Ampersand modules is changed causing a change in the CVSROOT/modules file. If I would want to roll back to rev. A, I would have to restore the previous version of the CVSROOT/modules file, to ensure that the Ampersand modules are defined correctly. Unfortunately, yes, that's what you'll have to do. CVS's configuration management support in this respect is rather lacking. For maximum control, you could use a makefile or a script in the project itself, which checks out the required sub-modules. An advantage of this approach is that your script/makefile can specify exactly which tag to retrieve - you can't do that with ampersand modules. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Help Required in CVS
Hemant Thakre wrote: 2) Another problem which I'm facing after upgradation is *CVS Time stamping problem. *When I checkin or commit any file to cvs server. It shows diff. time stamp for checked in file which is around six hours less than current time. We use ntp for time synchronisation in our premises. So all the workstations and servers are having exactly same time (GMT IST). I dont know from where CVS is picking up this time. Please let me know any solution if somebody came across these kinda problem. Thanks in Advance CVS always stores files using UTC. UTC is, IIRC, the default time displayed for the 'cvs log' command. Which time zone are you in, and which time zone do your PCs show? Can you provide copy-and-paste examples of the time output that you're getting, and indicate what you were expecting to see? -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS-Directories disappear when uploading per SFTP-Client
Dennis von Ferenczy wrote: Yes. Get a CVS client for your local machine and do your cvs commits from there behind the IDE's back. On the CVS server == web server, use the loginfo hook to keep a reference sandbox up to date, from which the web site operates. https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC158 Thanks for your advice. But what will be the advantage? If I get you right, then I would have to do a commit every time I want to test the changes in my scripts, even if I have changed only a single line of code - and even if the code is buggy. Right now I work locally, have the files mirrored using SSH (I'm not sure if cvs can use SSH) can immediately try my changes and if everything works as desired I do a commit. Like this I can always be sure, that code in the repository is actually code that is working correctly. It sounds like you use your production environment for testing. Good configuration management practises dictate that you should never do that. Configure your local machine to behave the same way as the production machine. Test on your local machine. If you do not do this, then sooner or later you *will* crash your production machine. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: query
Russ Sherk wrote: You are correct Jim. It should be used together with other metrics to aid in determining the general health of a particular load or to see general trends. E.g. we used to parse the logs between builds and generate a list of changed files grouped by log entry and PR #. It provided a snapshot of the changes that was easy to scan. (You could see what changed, how much changed etc.) This was particularly useful for TV. Now _that_ sounds like useful information. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: login cvs from Linux on windows directory
Travos Xavier wrote: Hy all, I am using cvs from a linux platform and the cvs directory is on a server. My problem is that the cvs directory for the server in on a windows host D:\CVS. How to login ? Im doing :pserver:[EMAIL PROTECTED]: because it is not linux directory /usr/cvs for example. Sounds like your server is CVSNT. I _think_ the syntax is something like :pserver:[EMAIL PROTECTED]://D/CVS/ - poke around the cvsnt.com web site for details. If that doesn't work, you could always try the CVSNT client - it has been back-ported to UNIX. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: migration of CVS repositery from one machine to another
Todd Denniston wrote: [...] moving a repo is covered in the manual[1]. basically: 0) get everyone to do a final checkin and then release their sandboxes (mainly prevent confusion later). 1) Back up the repository [2]. 2) take the backup to the other machine. 3) restore from backup. 4) configure the machine to serve cvs. 4a) test the configuration, including all scripts. 5) update everyone's CVSROOT values. There is, of course, the possibility that someone might forget that the migration is happening, and check in a change to the old repository while the migration is in process. To eliminate this possibility, just create an empty file named CVSROOT/writers between steps 0 and 1. This also adds step 6: delete CVSROOT/writers file. Step 5 is actually a rather difficult task. In order to make future migrations easier, I recommend that your server's actual machine name is *not* the one that is published to the users. Instead, set up an alias, which your system's DNS resolves to the actual server. That way, you can eliminate step (5) in all future migrations. IOW, set up an alias in your DNS entries, called cvs.yourcompany.com. A DNS lookup resolves cvs.yourcompany.com to the actual machine. Then, in future migrations, you simply perform all the steps above, except step 5 now becomes: Change DNS entries to point to the new machine. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Working on sources in parallel
Paul Sander wrote: CVS notices the conflicting changes and produces a working copy of the file that contains Person1's removed lines and Person2's inserted lines, with special mark-ups to draw attention to the problem. It also leaves copies of both contributors in the user's workspace. Not quite. CVS will only rename your working copy to .#[filename].[cvs revision]. To see the other person's contributions you need to use 'cvs diff' on the pre- and post-modification revisions. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: query
Hridyesh Pant wrote: Hi All, Is there any way to find out how much liles added or removed in a file between two dates. [note: please choose more descriptive subject lines. query is rather vague.] Not easily, no. Between one revision and the next is quite simple - just look at the output of 'cvs log'. I'm curious - what use could this information possibly be, anyway? -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Repository Access
S I wrote: Hi Class! Currently our CVS repo has 3 main separate projects running under it. By default when I create a new unix user; I give them access to the whole repository, however, some folks have been editing files in projects they were not supposed to. How can I ONLY and specifically create or modify the access rights privileges of only few specific people w/o wreaking havoc on the whole repository? And by default if they're not listed in that file then that means they have access to all projs? Is there a way? Use your operating system's access control system. Create a group for each project, and assign people to the groups they are allowed to be in. You will have to determine, in conjunction with your project leaders, which projects new users will have access to, by default. And, of course, get the managers and project leaders on side to explain that changing project files they haven't been assigned to will result in disciplinary action, up to and including termination. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Repository Access
S I wrote: cvs_acls? Ok thanks. I have to research that. Is that a 3rd party tool or part of CVS? It's part of the source code distributed from www.cvshome.org. Download the tarball (or check out the source) and cvs_acls will be in a directory named 'contrib'. cvs_acls provides more fine-grained control over access - it allows, for example, control over who can check into branches, and so on. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: query
Russ Sherk wrote: On 6/16/05, Jim Hyslop [EMAIL PROTECTED] wrote: I'm curious - what use could this information possibly be, anyway? Usually this information is used by managers to determine churn. Bigger churn (more files/lines changed) means bigger risk. Not if there's a proper set of unit tests in place. I'm always skeptical of raw numbers like this being used for any meaningful analysis. I don't think simply counting the number of lines added or removed is a good indication of risk. Suppose the tool reports 100 lines added, 100 lines removed. Does that mean one line was changed 100 times? 100 lines were changed, one time each? Changing one line 100 times carries less risk than changing 100 lines once. And unless FishEye (or any other software) performs a fairly complex analysis of exactly which lines were added and removed, you won't know where on that spectrum your count of 100 lines added/removed lies. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Recovering from Attic
Aaron Jackson wrote: Ok, if there is a directory in a project that had three files in it and they were all removed to the attic with cvs rm at different times and you want to recover all three files (say 3 could be 100+ files in some cases) but they all have different versions on them. How could you check the version just before the version that was marked as dead and moved to the attic? I did manage to recover something that had been tagged, but in this case many of the files would not be tagged in a version. If there are many files, then I think you'll have to write a script to do this: - create a dummy file with the correct name - issue a 'cvs add' and captures the output of the add command, e.g.: cvs add: Re-adding file `test.txt' (in place of dead revision 1.3). - parse the above message to find the dead revision number - subtract 1 to get the last good revision number - issue the command cvs update -p -r[rev number] filenamefilename -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Sorry about this newby question
Ah, I didn't understand the part about the attic. I'm trying to build a system that will still work when the server is off-line. I'll have to scratch my head about that one. No doubt I did the init by mistake. Before I did it, it adding caused it to yell at me about CVSROOT and after it did not yell, so it seemed right to me, but as I said, I'm new. Thank you. Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Sorry about this newby question
Hello, I apologize in advance for what is no doubt a foolish question, but I'd greatly appreciate it if a kind soul could set me straight. I've just checked out a CVS archive (I have Fedora Core 1 running on a laptop, if that matters). export CVSROOT=/usr/local/cvs mkdir $CVSROOT cd $CVSROOT cvs init cvs -d:pserver:[EMAIL PROTECTED] login cvs -z3 -d:pserver:[EMAIL PROTECTED] co modulename (I pasted in the instructions that were on the site, so I'm pretty sure I did it right.) Now I want to add a file to the local repository (by that I mean the sandbox). But I am on a laptop, not connected to the Internet. cd modulename cp /home/jim/newfilename . cvs add newfilename and the system objects unknown host ... (it names the host from which I checked out the material). Of course, I can see why it would give me such an objection on a commit or an update, but should I be getting it on an add or a status? It isn't the case that I have to be connected, is it? Sorry; I'm just not seeing something. Thanks, Jim Hefferon ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Retrieving dead files from the Attic
S I wrote: Here's another question I have on the same topic: If a file is removed from CVS properly (by rm, cvs rm, cvs ci), what gets committed to the Attic exactly? Both the file and its sister comapnion file,v or just the latter? The original file is never copied into the repository. When you 'cvs remove' a file, CVS adds a new revision to the ,v file, with the state dead, and the file is moved into the Attic. I still have not managed to retrieve my lost files from the Attic, executing the 3 commands I listed. They simply don't work and retrieve new files with zero or empty cotent. Help! Keep in mind that just because a file is in the Attic does not mean it is completely dead. It only means that the *trunk* is dead. Unless the file was explicitly checked into the Attic directory (which is unlikely, because the developer really has to go through hoops to do that) then everything can be done from your client. What does a 'cvs log' show for one of the files? (You can trim the log messages themselves, but please keep intact the header and the revision state info, e.g.: RCS file: /cvs_repository/conversations/factory/save.txt,v Working file: save.txt head: 1.1 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 1; selected revisions: 1 description: revision 1.1 date: 2003/03/09 16:26:19; author: Jim; state: Exp; [log message trimmed] = -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Problems with branching
rakesh mailgroups wrote: Hi all, I have found branches that i have created in cvs are not showing for other users and vice versa. Does anyone know why this is? I have never heard of such a problem. What exactly do you mean by not showing for other users? Please provide more details: exactly what commands did you run, what was the expected output, and what was the actual output you received? Also, which version of CVS (both client and server) are you using? -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Restoring deleted revisions (was: Branch Numbers)
Hridyesh Pant wrote: Thanks a lot Jim. Is this version of cvs is stable? right now we are using cvs 1.11.17. Is is ok for me to go 1.12 version? It should be, yes. 1.12 is very close to being promoted to the next stable version. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: trigerring several actions on commit
Guillaume Rousse wrote: I had a small look in the list archive and in the on-line manual without being able to find an answer: can I trigger several actions with a single commit ? My own tries make me think that only the first line with a regexp matching the commit directory is used, and subsequent ones are silently ignored. I could use a wrapper scripts encapsulating the different tasks, however I don't want to use the same list of task for all the different parts of a repository. In other terms, I'd like to do something as: ^foo report-mail ^foo/www extract-website Meaning sending mail for any commit in foo modules, and additionaly extracting web pages for the www subdirectory. ^foo foo_commit.sh ^foo/www foo_www_commit.sh where foo_commit.sh and foo_www_commit.sh call whatever scripts you need. Or, have a single foo_commit.sh script, which uses `cwd` to determine if it's in the www subdirectory, and if so, invoke extract-website. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Restoring deleted revisions (was: Branch Numbers)
Hridyesh Pant wrote: Hi Jim, As per ur suggestion i made cvsadmin group.but now the user can not execute cvsadmin -l filename to lock the file. CVS 1.12 can be configured to allow non-admin users to execute specific cvs admin sub-commands. Have a look at the UserAdminOptions at https://www.cvshome.org/docs/manual/cvs-1.12.12/cvs_18.html#SEC206 -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How to get started
Rondal Ellifritt wrote: I have recently been hired into an existing development group. One of my tasks is to get the group using version control. Quite a challenge, from your description. Maarten has given you some excellent tips. Out of all of these, I think your first priority *has* to be to separate the production environment from the development environment. I know you're new to the company, but I'm sure if you start enough casual conversations, you'll get a large number of horror stories about problems that occurred because of this mixture - use this as ammunition to convince people. Also explain that separating development from production is not _your_ way of doing things - it is a widely accepted, industry standard Best Practise. Nowhere have you mentioned developer training in CVS. Do the developers already know how to use CVS? If not, that is a critical step that must happen before you do anything. The developers must understand and be comfortable with basic version management concepts and the basic CVS commands if you want any hope of achieving your goals. Along the way, you will likely encounter many excuses for not doing things the new way: Oh, it's only one minor tweak. I don't have time to do it right - I've got a deadline (your response: If you don't have time to do it right, when are you going to have time to do it over? and don't wait for an answer - it's a rhetorical question). Gently but firmly remind them that these shortcuts are what got them into the current mess they're in (and don't be afraid to use the word mess - if the other developers have a shred of professional pride, they know in their hearts the situation is a disaster waiting to happen). As you progress, you will likely have dozens of questions. Feel free to post them here - that's what this list is for ;=) -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS update -j branch-tag failes to merge
Asbjørn Sæbø wrote: On Fri, May 13, 2005 at 03:58:12PM -0400, Jim Hyslop wrote: What version of client and server are you using? Both are 1.12.9 Hmmm... I just tried it with 1.12.12, and it worked OK. Can you upgrade to the latest versions and try again? -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS update -j branch-tag failes to merge
Asbjørn Sæbø wrote: On Fri, May 13, 2005 at 10:04:59AM +0200, Asbjørn Sæbø wrote: I have a CVS module (named ldas) where I would like to merge the contents of a branch into the trunk. According to the documentation, is seems that I should be able to du this using cvs update -j branch-tag. However, this does not work. No merging takes place, the files on the trunk do not receive the changes from the branch. [...] [EMAIL PROTECTED]:~/ldas/utvikling$ cvs update -j dev_20050413_b ldas However, when I changed into the ldas directory, and did the update, it worked: [EMAIL PROTECTED]:~/ldas/utvikling$ cd ldas [EMAIL PROTECTED]:~/ldas/utvikling/ldas$ cvs update -j dev_20050413_b . [Much retrieving and merging] Is this difference between naming the module/directory and standing in the module/directory expected behaviour? No. I just tried it with cvs 1.11.20, and it worked OK: C:\cvs-test\jimcvs -d \cvs_repository tag -r brach_base -b abranch cvs tag: Tagging . T test.txt C:\cvs-test\jimcvs up -r abranch cvs update: Updating . C:\cvs-test\jimecho branch changestest.txt C:\cvs-test\jimcvs ci -m branch changes test.txt Checking in test.txt; \cvs_repository/cvs-test/jim/test.txt,v -- test.txt new revision: 1.2.2.1; previous revision: 1.2 done C:\cvs-testcvs up -A jim cvs update: Updating jim U jim/test.txt C:\cvs-testcvs up -j abranch jim cvs update: Updating jim RCS file: \cvs_repository/cvs-test/jim/test.txt,v retrieving revision 1.2 retrieving revision 1.2.2.1 Merging differences between 1.2 and 1.2.2.1 into test.txt What version of client and server are you using? -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Questions on pserver authentication
Todd Foster wrote: I am trying to determine how pserver authentication works. I understand when you do a cvs login that it creates ~/.cvspass file. Therefore, I'm guessing that whenever you are running cvs commands cvs blindly combines the USER from whichever method wins (either using the pserver info found in the local working copy or in the $CVSROOT or in the -d) and uses the password from the ~/.cvspass of whoever is running the commands. Is this correct? No, there is nothing blind about this. CVS determines the user ID from the CVSROOT information. It searches for the CVSROOT information in this order: 1) the global -d option 2) the file ./CVS/Root 3) the CVSROOT environment variable CVS then parses the CVSROOT information, and if the :pserver: method is specified, it looks up the CVSROOT in $(HOME)/.cvspass (note that it is not necessarily ~/.cvspass - $HOME is frequently set to ~). So, if user1 goes into a cvs directory created by user2 and tries to do cvs commands in there, it uses the username found in the local working copy (user2) and combines that with ~user1/.cvspass and authentication fails. One way around that is to override the user explicitly to user1 with the cvs -d option. However, this is a very annoying way to get around the problem. You could delete the file CVS/Root, and make sure each user has the CVSROOT environment variable is set. If you're using *NIX, you could create an alias: alias cvs=cvs -d :pserver:[EMAIL PROTECTED]:/path on a per-user basis. Or you could wrap CVS in a script: # cvs-wrapper.sh cvs -d :pserver:$(USER)@server:/path $@ (or whatever the syntax is for 'all command line arguments - I'm not very experienced at shell scripts) and get everyone to use cvs-wrapper.sh instead of cvs. What I'm really wondering, is what does the pserver authentication do if the username is omitted from the pserver CVSROOT, then what happens? I haven't tried it, but you'll probably get an error, since the CVSROOT format for :pserver: requires a user name. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Restoring deleted revisions (was: Branch Numbers)
Hridyesh Pant wrote: Hi Jim, I need ur help,some how i deleted 1.1 revision of some files.can i restore this revision. The only way to actually delete a revision of a file is using the 'cvs admin -o' command. There is no way to undo that action, except by restoring the repository file from your daily tape backups. For example: if i have 1.2 revision of these files , can i make 1.1 revision which is copy of 1.2 revision? You could, but what would be the point? Is there any cvs command to do this. No. Unless revision 1.1 has critical information in it, I wouldn't worry about it. If you feel you absolutely must have the revision 1.1 available, then here's what I suggest (others may have better ideas): Before you do anything, back up your repository as it sits right now. That way, if any of the following steps screw up, you can simply restore from backup. If and *ONLY* if you are sure there have been no check-ins, tags, or other modifications to the file since the revision got deleted, then simply restore the ,v file from your tape backup into the repository. Make sure nobody else is trying to access these files while the restore is in process (you can create two empty files, called 'readers' and 'writers', in the CVSROOT directory to lock everyone out of the repository temporarily; delete the files when done). Otherwise, if there is any doubt, then restore the repository file *into a different location in the repository*, check out revision 1.1 of the file, copy it into the good working area, and check it in on a branch. It will not be revision 1.1, but at least it will be available for inspection. As an example, suppose the file you want restored is big_project/main.c. Have the file restored to, say, $CVSROOT/temp_for_restore/big_project directory. Then issue the following commands: cvs co big_project cd big_project cvs tag -b -r1.2 revision_1_1 main.c cvs up -r revision_1_1 cd .. cvs co temp_for_restore/big_project/main.c cp temp_for_restore/big_project/main.c big_project cd big_project cvs ci -m Revision 1.1 restored from tape backup main.c Right now i am not able to send mail to info-cvs@gnu.org.so pls help me. I've cc'd the list with my response. -- Jim p.s. it's always best to start a new topic by creating a brand-new message, not by replying to an old one. Your question has nothing to do with the previous discussion on branch numbers, and (assuming it made it to the list) might have been ignored by someone who's flagged that thread as not interesting. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS migration question
[EMAIL PROTECTED] wrote: I've been thinking about this since reading it on CM Crossroads this morning. I don't think it would be too terribly complicated. On the server side, I think it's just a matter of packing up the entire repository and ftp'ing it to the new server (or just copying it if you have a samba share). That's the bulk of it. You would have to update (or more likely rewrite) any scripts, such as commitinfo, loginfo, etc. My only concern is whether or not you'd have to worry about the ^M end-of-line problem between windows and Unix. Nope. RCS file format always uses a plain ASCII LF character as the line terminator, regardless of the platform the RCS file lives on. It's the client that translates LF into the appropriate line terminator for the client platform. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS and Images
Mychael Scribner wrote: I have a simply little question. I do a lot of web based project that often have images. Is their and do's or don'ts that I be watching for with images. Should I not include them when I import a project? There's no reason to exclude them. Just make sure you mark them as binary when you add them - either add the extensions to $CVSROOT/CVSROOT/cvswrappers, or explicitly use the '-kb' option with the 'cvs add' command. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: watch on dir
Pedro Hernandez wrote: Hello folks! cvs 1.11.20 on Whitebox Linux 3 I'm trying to make a directory watched by default, reading in Cederqvist Command: cvs watch on [-lR] [files]... ... Is this a bug in cvs, the doc or in my head? It's a bug in CVS. The workaround is to issue the command from within the directory, and do not specify anything for [files] when you issue the command: cd wt cvs watch on -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Can't checkout to my C: root directly *PANIC* Admin Files Missing
Mark D. Baushke wrote: If you see that you are indeed configured to use TopLevelAdmin=yes, then Arno Schuring's analysis that you are unable to create and populate a C:\CVS directory is likely the root-cause of your problem. I think the analysis Arno provided is exactly right, and has nothing to do with the TopLevelAdmin option. From any working directory, if you create a directory named CVS (or 'cvs' on Windows, since it's case-insensitive) then _without changing directories_ issue just about any CVS command, you'll get the PANIC error message. The red herring in this case is the fact that the current working directory also happens to be the root directory. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: What exactly is HEAD anyway?
Andrew DeFaria wrote: The more I look into CVS the less I understand. Perhaps you can help me... When using -r HEAD I do not seem to get the latest revision on the trunk: As you've found, 'HEAD' means the latest revision on the trunk for all commands except 'diff', where it means the latest revision of the branch that is checked out. I don't know how this inconsistency came about, but for backwards compatibility it's not likely to get fixed. Instead, the feature branch (CVS 1.12.x) has added new special purpose tags so that you can always specify the tip of the trunk, the tip of a branch, the base of a branch, and so on. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Branch Numbers
SUBRAMANIAN, SARAVANAN (SBCSI) wrote: Hi all, How Branch Numbers are formed Internally in CVS. I read the manual it is really confusing. We have two branches, after we created the second branch, when the developers start committing the files, I found out that one file is committed with 1.12.2.1 And other with 1.1.4.1 Please help me found the why there is a difference in the above? Larry and Kaz have given some excellent basic information to answer your question. I will add this, though: forget about it. Revision numbers should, for the most part, be treated as black boxes that have no meaning to you and me, only to the program itself. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking a Branch
SUBRAMANIAN, SARAVANAN (SBCSI) wrote: Hi I need to lock a Branch, so that no one can check out or check in some information into it. First of all, do you really need to lock the branch? Can you not trust your developers? I don't have access to the CVS host machine, but I am connecting it through the CVS Binaries That will make it more difficult. You need to install scripts on the server in order to do what you want. One script is the cvs_acls script that is contained in the source distribution (download the source from www.cvshome.org). -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: contrib directory?
[EMAIL PROTECTED] wrote: This is like the third reference I've seen to a contrib directory... where is it? As I said, it's in the source code distribution. Download the source code from www.cvshome.org. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Renaming a branch
David Leskovac wrote: Sorry for the basic question but I need to implement a new branch naming scheme want to make sure I am doing this correctly. To start this process, I need to rename several existing branches. Would this work for each branch to be renamed?: cvs rtag -b -r original_branch_name new_branch_name module cvs rtag -d original_branch_name I am aware of the -B argument to rtag. But, the version of cvs that we use is so old (1.11.1p1) that it pre-dates that argument. That will probably get you where you want to be, although it doesn't really do what your stated goal is (to rename the branch). It will create a new branch and delete the old branch. The effect will be the same, but be aware that you will be branching off a branch. Suppose, for example, that the tip revision for a particular file on original_branch_name is 1.2.2.2: Before branch add and delete: 1.1 --- 1.2 --- ... \ + --- 1.2.2.1 --- 1.2.2.2 after branch add and delete: 1.1---1.2--- ... \ +---1.2.2.1---1.2.2.2---X --old branch (effectively dead) \ + ---1.2.2.2.2.1 -- new branch 'cvs co -r new_branch_name' will retrieve the correct branch. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Lock on Trunk
Dean Do wrote: Hi, I have a question on access control. Is there a way to prevent all commits on the main trunk and allow commits on branches only? Once the changes on the branch are reviewed and approved for merging into the main trunk, then the main trunk can be manually opened up temporarily for those changes only. Please advise if there's a way to implement this type of controlled access. Yes. Have a look at the cvs_acls script, in the contrib/ directory of the source distribution. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Question about binary distribution
(gnu.cvs.help trimmed from recipient list; I can't access it) HSP wrote: hello, i downloaded cvs-1-11-20.zip from https://ccvs.cvshome.org but i can´t find information about wich windows versions are supported. Is Windows 2003 server suitable for cvs server ? thanks in advance!! If you're using Windows as your server, then you probably would be better off using CVSNT on your server: www.cvsnt.org Clients can use either CVSNT or cvshome's CVS. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Idea for reducing disk IO on tagging operations
Dr. David Alan Gilbert wrote: 2) I could do with a better under standing of the directory locks; pointers? I've read the top of lock.c but it still doesn't tell me enough; for example there seem to be multiple lock files used - but then surely the creation of them isn't atomic? Or is there one lock file used for both reading and writing? The locking process is explained in the manual, at https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_2.html#SEC17 -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Checkout after a change
[EMAIL PROTECTED] wrote: The example they give is with unix, how would I do it with linux (Fedora C3, I think it is). Same principle. Remember, Linus *is* a port of UNIX. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Can't specify username with cvs-rsh
On a shared webhost, my username is [EMAIL PROTECTED] and the hostname is jimrandomh.org. With ssh, I can log in fine with ssh -l '[EMAIL PROTECTED]' jimrandomh.org. However, I can't find a way to get CVS to pass the correct options. If I use export CVS_RSH=ssh cvs -d :ext:[EMAIL PROTECTED]@jimrandomh.org:/cvs init Then it misparses this as user:jbabcock, host:[EMAIL PROTECTED] If I use export [EMAIL PROTECTED] cvs -d :ext:jimrandomh.org:/cvs init then it just ignores the USER environment variable. There doesn't seem to be any option to specify the username separately (like ssh's -l). So, how do I use CVS if my username contains an @ character? ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Equivalent to cvs log -rBASE::HEAD?
I found this question in the archives, but never saw an answer. Is there a way to get 'BASE' to work with 'cvs log'? Thanks, jim From: Slawomir Nowaczyk Subject:Equivalent to cvs log -rBASE::HEAD? Date: Wed, 29 Sep 2004 17:57:49 +0200 Hello, I would like to see cvs log messages for all the files and revisions which will be updated by next cvs update command -- to get an idea as to what has been changed. Ideally, I would like to do cvs log -rBASE::HEAD But log -r switch only accepts revisions, not tags (according to the documentation). Somehow, the HEAD is working, but BASE is not (I get no revision `BASE' in ... error message). I can imagine checking each file's currently checked out revision number and calling cvs log once per file... but is there an easier solution? Thanks in advice for any advices. -- Best wishes, Slawomir Nowaczyk Grossman's Law: Complex problems have simple, easy-to-understand, wrong answers. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Info-cvs Digest, Vol 25, Issue 35
We check out the entire repository (on several tags--e.g. DEV, PROD, etc.) and use glimpse (by Udi Manber) to generate an index. It is possible to generate the index w/o actually checking out onto a disk by using a pipe, but we get a lot of milage out of our checked out version. Glimpse can be found here: http://webglimpse.net/index.php?dir=subdownloadspage=download.html#bins Date: Tue, 21 Dec 2004 10:47:34 +0100 From: Riadh Elloumi [EMAIL PROTECTED] Subject: cvs search engine To: info-cvs@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii; format=flowed Dear all, Is there any seach engine for a cvsroot tree? I would like to google our archived documents like sources (C, Java, etc), docs (Microsoft Word, PDF), etc. Any help is greatly appreciated. Riadh. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Are there plans for a CVS C API?
Interesting. This could be quite useful. I can't wait to look it over. Thanks -- JimLane -Original Message- From: Alexander Taler [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 7:55 PM To: Lane, Jim; [EMAIL PROTECTED] Subject: Re: Are there plans for a CVS C API? Jim == Jim Lane Lane writes: Jim To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Jim Subject: Are there plans for a CVS C API? Jim Date: Mon, 6 Dec 2004 10:13:17 -0500 Jim Are there any plans for a CVS C API? Or, is there one available that I Jim am unaware of? Jim We have a lot of Perl scripts that call CVS and in some instances where Jim performance is a consideration, we would like to speed things up by Jim linking C programs to a CVS library and calling CVS via direct API Jim calls. Hi, depending on your needs, and what the performance issues are, there is also a Perl version of LibCVS which is already available as a feature-incomplete alpha. Performance is far from lightning-fast, but it can save you the overhead of opening connections many times. https://savannah.gnu.org/projects/libcvs-spec http://libcvs.cvshome.org/ Alex -- https://savannah.gnu.org/projects/libcvs-specAccess CVS through a library. PGP: ID: 0x23DC453B FPR: 42D0 66C2 9FF8 553A 373A B819 4C34 93BA 23DC 453B According to you, why to people pre-plan their funeral? -- Question on an unsolicited survey from a local funeral home. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Are there plans for a CVS C API?
Are there any plans for a CVS C API? Or, is there one available that I am unaware of? We have a lot of Perl scripts that call CVS and in some instances where performance is a consideration, we would like to speed things up by linking C programs to a CVS library and calling CVS via direct API calls. Thanks -- JimLane ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Ignoring whitespace and CR/LF when checking into repository
Antony Paul wrote: Hi all, Is it possible to tell cvs to ignore difference in white space and CR/LF when committing changes to a file. This is creating lot of problems since different developers use different editiors and OS. no, and they will not consider the simple solution of just treating all files as linux/binary mode, and keeping cr if there and dropping if not, but never translating a \n to a \r\n. There is ALWAYS a \n, on all system commonly used, obscure systems are doomed to have their own difficulties. and modern compilers will handle either rather gracefully. rgds Antony paul ___ 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
Re: Ignoring whitespace and CR/LF when checking into repository
Antony Paul wrote: Hi all, Is it possible to tell cvs to ignore difference in white space and CR/LF when committing changes to a file. This is creating lot of problems since different developers use different editiors and OS. Oops yeah I menat sure, all you need to do is grab cygwin for CVS, install default line endings linux style, and that will work. There is a one line modification you can make to CVS to make it open the file binary under windows, if you are able to build it. There are probably various flavors which work, but do NOT use the win32 native version, grab something more like the cygwin port of cvs... as slow and stupid as that is, the win32 people did it wrong, and won't consider fixing it. rgds Antony paul ___ 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
Support for CVS-1.12.9
Title: Support for CVS-1.12.9 Is CVS-1.12.9 being supported? I rarely, if ever, see 1.12.9 mentioned in this mailing list and all questions/problems/bugs that I sent to this list or the bug list have been met with stony silence. Have I made a mistake upgrading to 1.12.9? Thanks -- JimLane ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Support for CVS-1.12.9
That makes sense. I will be careful about keeping my mail plain text and attachment free. My last message to info-cvs did wind up in the list: http://lists.gnu.org/archive/html/info-cvs/2004-08/msg00011.html, but received no response. I don't claim to be a great author, so I may well have not explained the question well enough for anyone to understand what I was asking.Likewise, my message to bug-cvs went unanswered: http://lists.gnu.org/archive/html/bug-cvs/2004-07/msg00138.html This, coupled with my seeing very little about 1.12.9 mentioned in info-cvs has me wondering. Anyway, thank for the heads-up -- JimLane -Original Message- From: Jim.Hyslop [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 3:52 PM To: Lane, Jim; '[EMAIL PROTECTED]' Subject: RE: Support for CVS-1.12.9 Lane, Jim wrote: Is CVS-1.12.9 being supported? I rarely, if ever, see 1.12.9 mentioned in this mailing list and all questions/problems/bugs that I sent to this list or the bug list have been met with stony silence. Have I made a mistake upgrading to 1.12.9? I think it's more likely a problem with your messages getting out. I had a quick look at the archives, http://lists.gnu.org/archive/html/info-cvs/2004-09/index.html, and didn't see anything from you in September. Another possibility might be the MIME encoding - some people on this list don't read MIME-encoded messages (not everyone uses a GUI mail client ;-). Try asking your questions again, and post using plain text only. I will try to remember to reply to any mesages from you, even if I don't know the answer - that way, you'll at least know your posts are getting through. -- 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: /#cvs.lock): No such file or directoryctory for some directory inrepository
Hi Arthur I hope cvshome people will not mind a quick discussion, too much, on an alternative product as it is relevant to this thread. From: Arthur Barrett [EMAIL PROTECTED] Using a sandpit with CVS (cvshome) and CVSNT clients is dangerous and not supported. Since CVSNT is available for all platforms I suggest you use it on the linux box and client. Thanks for that. I will evaluate your suggestion, certainly having a consistent cvs client product on all platforms sounds like a good move. I guess one could run cvshome on windows via cygwin or similar but it seems a rather long way round. 2. Always commit from either linux OR windows. I take it this is to avoid linefeed issues in source? Not because of incompatabilities of CVSNT metadata between platforms? Thanks Jim Email the way you want it - scanned for viruses and unwanted content by emailsystems Information regarding this service can be found at www.emailsystems.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: /#cvs.lock): No such file or directoryctory for some directory inrepository
Hi Doug Thanks for your input. I think I hold a minority position here, but I would just like to add my comments in case I didn't communicate my position well and you misunderstood me. What you are suggesting, and is also suggested in the above postings, is having 2 sandboxes, 1 linux and 1 windows, right? Ok but it sounds like a typical case of us working round the tools rather than them working for us. Actually, since line endings are different between Windows and Linux, I don't see how you could safely do any different: If you edit in Windows and Alice edits in Linux and you share a directory, chances are extremely high that Alice will introduce lines with missing CR's and you'll introduce lines with extra CR characters. To me, it's a bit like this: If you check out in English and she checks out in Spanish, you can't really use the same checkout without getting gibberish. grin That's true except that most decent editors (the ones we use anyway) can be set to detect line ending type and stick with it, and we standardise on unix line endings. The only time we encounter problems like this is where someone hasn't got their editor set up right, and that can be fixed as a one-off with dos2unix. I believe we have the line-endings-in-source issues dealt with, or at least at a manageable minimum, and we have run ok for 2 years or so. My problem here is the cvs tools writing their system files differently according to OS, which doesn't seem a good idea to me. I think I have expressed myself badly. Our developers are working on both windows and linux -at the same time-. Either with 2 dev boxes, or using VMware to run the other OS, with a partition shared between the 2. What is being suggested here is using commit to propogate changes between a given developer's OS-specific sandboxes during development. I am talking here about 'ok that fix builds under windows, lets see if builds under linux'. In our case right now this class of commit would not be done, and I can't see how this won't lead to an increased risk of nonsense in the repository. Maybe I'm splitting hairs but even if the risk is small it just doesn't seem a good idea. I can't believe our situation is all that rare. Now I have written that I'm starting to think that I am complaining in the wrong place. It is probably WinCVS or another product that is writing these badly formatted files. linux cvs broke, and I posted a message concerning how to fix it, but it is not to blame if some other product it messing up its files! Hmm. My apologies for wasting everyone's time. Cheers Jim Email the way you want it - scanned for viruses and unwanted content by emailsystems Information regarding this service can be found at www.emailsystems.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: /#cvs.lock): No such file or directoryctory for somedirectory inrepository
2. Re: /#cvs.lock): No such file or directoryctory for some directory inrepository (Frederic Brehm) 4. Re: /#cvs.lock): No such file or directoryctory for some directory inrepository (Geoff Beier) 6. Re: /#cvs.lock): No such file or directoryctory for somedirectory inrepository (Todd Denniston) Fred, Geoff, Todd You have obviously thought all this through, and I have quite a lot to think about. It's clearly hopeless working with tools from multiple OSs on the same sandbox, and I guess I have been lucky so far, that's all. I think my preferred route will be to restrict tool usage to one or the other per developer, as the alternatives - multiple sandboxes, branches seem to me to add too much complexity and scope for error. Thanks a lot for your input. The free software community validates itself once again :) Cheers Jim Email the way you want it - scanned for viruses and unwanted content by emailsystems Information regarding this service can be found at www.emailsystems.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
/#cvs.lock): No such file or directoryctory for some directory in repository
I found a post in an archive regarding this issue which came quite close to an answer, but not quite. I thought I would share my efforts in case it saves someone some time. Here is the root of teh original thread: http://lists.gnu.org/archive/html/info-cvs/2002-09/msg9.html Environment: Running unix/Windows cvs clients on source located on a volume shared between OSs, shared using either Samba or Windows Services for unix NFS (I tried both). specifically, unix client: cvs (various versions 1.11.2 up to the latest stable release, under linux). Windows clients: WinCVS and the PushOK cvs proxy for VisualStudio. The server is a linux box running cvs 1.11.17, on slackware 9. Symptom: Running pretty much any cvs command on a client (unix or windows) results in something like the following: ... cvs stuff ... cvs status: Examining . /#cvs.lock): No such file or directoryctory for `/home/cvsroot/blah 'vs status: failed to obtain dir lock in repository `/home/cvsroot/blah cvs [status aborted]: read lock failed - giving up Fix: Run dos2unix (or similar) on the CVS/Repository file in the client directory. Note this problem is on the client, not the server. The problem is that the DOS EOL at the end of the path in CVS/Repository is interpreted as part of the path. This may be an incomplete fix, as I am a newvie running a cvs server, but it seems to have worked for me with no ill effects. Cheers Jim Email the way you want it - scanned for viruses and unwanted content by emailsystems Information regarding this service can be found at www.emailsystems.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: /#cvs.lock): No such file or directoryctory for some directory inrepository
Hi Todd From: Todd Denniston [EMAIL PROTECTED] Huge suggestion: Read the messages found here: http://www.google.com/search?hl=enlr=ie=UTF-8q=cvs+network.file.system+site%3Alists.gnu.orgbtnG=Search http://www.google.com/search?hl=enlr=ie=UTF-8q=cvs+larry+network.file.system+site%3Alists.gnu.orgbtnG=Search http://www.google.com/search?hl=enlr=ie=UTF-8q=cvs+samba+larry+site%3Alists.gnu.orgbtnG=Search Thanks for the suggestion, very interesting reading. In my case the repository is on a linux box accessed via :ext: CVS_RSH=ssh. From what I have read this is not a bad method. So I do not have problems with the repository accessed as a shared local drive as in some of the postings above. Always use a client that is native to the host you are doing your editing on! Never share directories between different OS's, do a full checkout on the host/OS you are doing the editing on, as some OS's will not use the same line endings. What you are suggesting, and is also suggested in the above postings, is having 2 sandboxes, 1 linux and 1 windows, right? Ok but it sounds like a typical case of us working round the tools rather than them working for us. But I get the feeling that is the recommended way - commit/update, often. Hmm. Committing something to a repository just in order to get it into the other sandbox sounds all wrong to me. As a common sense approach to version control, I try to get my people to a) not commit anything unless they are pretty sure it builds and works, b) put meaningful comments in the logs. This 2-sandbox strategy is going to mess that up for sure! If everybody is doing loads of commit/updates to copy between sandboxes during development, then there is an excellent chance that Alice picks up Brian's half-baked commit and that's him/her out of play trying to figure out what they just busted. Getting this surely very common scenario to work reliably with a shared directory would certainly go on my wish list. Specially since it -nearly- works ... no corruption of data as far as I can tell, just a weird error message. While we are talking about it, what it the point in being able to specify what kind of line endings you want when you check stuff out, if it isn't followed through? But hey ... if a cvs guru says don't go there, it will never work, then I will look at the alternatives, and thank him for the advice. But it seems to me a surprising weakness in cvs from the POV of cross platform development. Cheers Jim Email the way you want it - scanned for viruses and unwanted content by emailsystems Information regarding this service can be found at www.emailsystems.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
How can I view files with a specific tag in CVS? (follow-up)
If you are using the latest on the 1.12.x branch (1.12.9, I believe), you can use the cvs rls -r TAGNAME module-you-are-interested-in.The new ls and rls commands don't work if individual file names are specified, but seem to work fine on directory and module name arguments. -- JimLane Note: This is a follow-up. But for some reason it's no longer possible to answer postings older than 1 month. Very user-unfriendly if you ask me. Anyway, I still need some CVS help, see below... [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Anyone knows if there is a CVS command that can be used to see which files (and their version) that has been tagged with a specific tag? cvs -nq up -r tag-you-are-interested-in OK, that's fine, but I would like to see the version of each file too. The above command only shows file names... /Peter ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
taginfo logs all tagging
Title: taginfo logs all tagging
We track all tagging via a perl script called from the taginfo file. We recently upgraded from cvs-1.11.2 to cvs-1.12.9. One problem we're having is the previous versions of CVS only put an entry in the tag log (i.e. invoked the script) for files in which the tag actually changes. The new 1.12.9 version lists every file in the module being tagged, whether or not the tag is actually moved. Since our build system is tag-based, rather than branch-based, this amounts to HUGE tag logs.
We are using cvs-1.12.9 via the pserver on Solaris 8. The line in the taginfo file looks like:
ALL $CVSROOT/CVSROOT/log_tag_ops %t %o %r/%p %{sv}
FWIW - I've build the server with and without the --disable-old-info-format-support flag.
Does anyone know how to restore the old behavior of only logging files for which the tags are actually changed?
Thanks -- JimLane
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Commit script
On Mon, 22 Mar 2004, Fouts Christopher (6452) wrote: I'm playing CVS admin for my group. Currently during the commit process, one gets prompted for a commit edit message window for every file to be committed. This is of course impractical for a lot of files. How can I set up a script in rcsinfo to use the same commit message for ALL files to be committed? cvs commit -m Message Jim Wildman, CISSP, RHCE[EMAIL PROTECTED] http://www.rossberry.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Can wincvs graph all versions/branches for a module?
We use cvs on a Solaris box for managing our source code. Most of our group has never learned anything about it beyond clicking menu items in Jbuilder to checkout/update/commit. Now, we are trying to teach them how to actually use CVS. I am trying to make it easier by installing wincvs on the Windows boxes they use for development Some members are still complaining about all the things cvs won't do, and pining for Visual SourceSafe. (This really means they don't know how to do what they want in cvs, and don't want to learn.) So far, I have been able to demonstrate almost everything, except one. Apparently, VSS can show a graph of versions/branches for a module, and I cannot figure out how to do that in wincvs. The graph function seems only to work for individual files. Am I missing some way to do this? Thank you. -- Jim McMaster Sr. Software Systems Engineer Global Services Solutions Tools 303.673-7419 phone 303.661.6717 fax [EMAIL PROTECTED] StorageTek ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: file type
rom: Martin Marques [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 13, 2003 11:10 AM Subject: file type Hi, I have a repository with some .tex files that I use to give some courses. The thing is that I include images in the .tex and those images are in the repository as well. The problem is that I'm not sure if I added the files (.png images) with or without the -kb flag. cat CVS/Entries -or- type CVS/Entries depending on your ssytem - that has the -kb mark in it. (or not) My question so would be, how can I see if a file is considered binary in the CVS repository, and if not, how (if it's posible) can I change it so that no RCS is handled on them? -- select 'mmarques' || '@' || 'unl.edu.ar' AS email; - Martín Marqués |[EMAIL PROTECTED] Programador, Administrador, DBA | Centro de Telemática Universidad Nacional del Litoral - ___ 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: Checkout with \r's
Supposing something doesn't make it so. That's exactly my point. -Larry Jones Honey, are we out of aspirin again? -- Calvin's Dad ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Checkout without \r's
Okay - under Linux, 'how do I checkout WITH \r's?' that's easy - put em in the file, check it in, and check it out... but woe to the windows user - who now get's \r\r\n's. under windows, how to do the same? Well if I have complete control over all options, use cygwin CVS and UNIX style file endings - problem is that's an option, and I can't seem to convince everyone to use the same options. Otherwise, what I see is not what I get. If one is developing and working with both platforms, his tools better be able to work with each other's TEXT without difficulty. How can I even guarantee that the source used to build the same object on different platforms was the same? I know I see even more sign of segregation of text and binary in CVS today than in prior versions... it's really too bad that everyone knows and is comfortable with CVS... if only they had realized sooner, this mentality that 'what you checkin is NOT what you checkout' would not have been so concrete, and this ... would not be an issue. If there is no spoon...there are no bugs, and there IS no spoon. - Original Message - From: Larry Jones [EMAIL PROTECTED] To: Jim [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 7:04 AM Subject: Re: Checkout without \r's Jim writes: That's an assumption about the file that is incorrect... it didn't start with \r's in it... and I need them to not be there. Then it's not a text file, by definition, no matter how much you think it is. -Larry Jones Hello, local Navy recruitment office? Yes, this is an emergency... -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS Commit sets file time backward
Concurrent Versions System (CVS) 1.12.2 (client) When I do a CVS commit of a changed file (for example this morning) the timestmp of the last mod was : 8:31 after the commit the timestamp on the file was 1:09 (hmm seems my clock on my CVS server is off also... since at 8:32 it thought the time was 9:09) Jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Checkout without \r's
Under windows how can I checkout/update a file without \r's being stuffed in? It's definatly a source file and uses keywords to track version information. Jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Checkout without \r's
- Original Message - From: Larry Jones [EMAIL PROTECTED] To: Jim [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 2:42 PM Subject: Re: Checkout without \r's Jim writes: Under windows how can I checkout/update a file without \r's being stuffed in? It's definatly a source file and uses keywords to track version information. If it's a source file, then it's a text file. On Windows, text files have \r's in them. That's an assumption about the file that is incorrect... it didn't start with \r's in it... and I need them to not be there. Jim If there is no spoon...there are no bugs, and there IS no spoon. -Larry Jones I wonder what's on TV now. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Checkout with \r's
How can I check out a file on Linux with \r's ? As part of a build process I use a SHA1 of the source as part of the versioning information. The same code on both windows and linux should generate the same SHA1. If there is no spoon...there are no bugs, and there IS no spoon. - Original Message - From: Jim [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 6:39 PM Subject: Re: Checkout without \r's - Original Message - From: Larry Jones [EMAIL PROTECTED] To: Jim [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 2:42 PM Subject: Re: Checkout without \r's Jim writes: Under windows how can I checkout/update a file without \r's being stuffed in? It's definatly a source file and uses keywords to track version information. If it's a source file, then it's a text file. On Windows, text files have \r's in them. That's an assumption about the file that is incorrect... it didn't start with \r's in it... and I need them to not be there. Jim If there is no spoon...there are no bugs, and there IS no spoon. -Larry Jones I wonder what's on TV now. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Case insensitivity ad nauseum
We once had the minor problem that somehow files showed up twice (e.g. doing an update). It turned out that the case of the file itself didn't match the entry in the entries file. So cvs once reported the file from the entries file and then again while looking for unknown files. It behaved correctly, it just did the file twice. But that's something the local client needs to handle (I guess) and not the server. So I don't know if this has something to do with your actual work, I just thought I'd mention it. Yes - if you use a poor editor it will not preserve the case of the filenames. FAT32, NTFS both preserve the case, even if it doesn't actually USE the case... It is entirely feasible to leave CVS case sensitive and make a note somewhere that the responsibility of preserving the case is on the user. Jim OOP is a frame of mind, not a language. The difference between a bug and a feature? A feature's documented. What? if I press the enter key the program crashes and makes the computer reboot? ... Yeah... it says right here - feature - quick reboot Everything changes, what you hear today is gone tomorrow, and yesterday might as well never have been. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Case insensitivity ad nauseum
Jim.Hyslop [EMAIL PROTECTED] WeLl mAdE ArguMent... No, not at all. For example, of the 111 items in my home directory right now, 17 of them use upper-case letters in a meaningful way. Common practice is to name some things on Unix in a mixture of cases, e.g. Makefile, Imakefile, ChangeLog. That's not really the point... how many times do you maintain ChangeLog, CHangeLog, changeLog, changelog in the same directory? or Makefile and makefile? or .BASHrc, .bashRC, .BashRc, .bashrc ? Is there even one example of where it's logical to have the same name with a different case in a directory? I suppose someone could have abused the case sensitivity and used capital cases of file extensions as backups... 'main.c' backed by 'main.C' though this seems like a bad habit. The arguments presented about the case insensitivity are rather valid... Another point I'd like to make: labels are case-sensitive already. Oh great so now tags like 'CheckPoint' 'CHECKpoint' 'checkpoint' are all different? how useless is that? it's the IDEA of the word not the technical content of the word that should matter Sorry for the bitter sarcasm.. I wish I had made such a valid argument for the windows client maintaining \r's and not adding additional ones whens storing \n's received from the server ... I mean the unix client has no problem maintaining when there are \r's in the files stored in the repository, both to and from with no arbitrary descisions to attach \r's to \n's received from the server - leading to \r\r\n sequences in files. I even tried to touch the repositories I had to strip out the \r's since it appears that they 'shouldn't' have been there in the first place, but gave up and grudgingly accepted to use the cygwin port (and therefore the cygwin dll's which change weekly) which don't have a problem maintaining the correct characters for a line ending. Anyhow sorry I'm digressing... Unfortunatly looks like both issues lead to dead ends. OOP is a frame of mind, not a language. The difference between a bug and a feature? A feature's documented. What? if I press the enter key the program crashes and makes the computer reboot? ... Yeah... it says right here - feature - quick reboot Everything changes, what you hear today is gone tomorrow, and yesterday might as well never have been. - Original Message - From: Steve McIntyre [EMAIL PROTECTED] To: Jim.Hyslop [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 7:33 AM Subject: Re: Case insensitivity ad nauseum ___ 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: move away file.java
Move away errors - commonly occur under windows file systems because many editors lose the case of the file. A file which is all upper case or all lower case appears to be lower case, but in actuality is upper cased. A file with mixed case will appear correctly. I have run into this MANY times after editing with lame editors that saved files as all upper case. I use FAR by (www.rarsoft.com) and it displays the actual case of files... not sure how to do this otherwise... but you can try just doing a 'rename file.java file.java' which will fix the case ( unless it was actually in upper case when you checked it in - have to check CVS/Entries to see what it actually wants ) So - although windows uses long file names and allows cases - for backwards compatibility it assumes all upper case is lower case, and forgets to tell anyone - but apparently the test within CVS even on windows is case sensitive. Jim - Original Message - From: Matt Bishop [EMAIL PROTECTED] To: CVS-II Discussion Mailing List [EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 2:36 PM Subject: move away file.java (This is a repost--I tripped a few spam filters with the last one...) I get this error frequently when updating in a directory with 'cvs update -dP': cvs update: move away file.java; it is in the way C file.java I am running CVS 1.11.5 for Windows; server is 1.11.6 on Linux. If I blow away file.java, and re-update, the problem goes away for a bit, then returns. If I update the file directly with 'cvs update -dP file.java' the update works as expected. I've searched Cederqvist, but found nothing. Google doesn't offer much more. ___ 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: The idea isn't clear...
demand, you might have logical concurrence in different implementations. But, is this right? That's the way to work with CVS? No - actually everyone works on the same branch(trunk)(path?), occasionally when you go to commit there could be times where someone else has already commited changes, you'll get a warning about being not up to date, but then do an update, and cvs'll merge the changes in with the current changes (and if there's conflicts whcih get marked with stuff === other stuff though I'm not sure whether the top or the bottom is more recent... it's ususally easy to tell which is the correct one... branches are more for after having released a version, and after continued development, you have to go back to the release point and make mods... then bring that small branch back into the main tree Regards, Giovanni Giazzon ___ 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: new feature.
The general recommended CVS usage model is that the repository be considered a whole entity. Thus, you tag the entire repository the way it should be for a particular release, whether it be a full release, or a partial delta. I *think* you could define a module as having parts of all modules and then tagging that single module would tag everything in the CVS tree... http://www.cvshome.org/docs/manual/cvs_18.html#SEC157 C.1.1 Alias modules ... as if the list of names aliases had been specified instead. aliases may contain either other module names or paths. . Extra tags on files cost almost nothing, and by properly maintaining your tags, you can re-generate your deltas trivially using cvs diff -rtag1 -rtag2, which will generate no output for files that have not changed between tag1 and tag2. Is this something you're already doing with another revision control system? I can't think of any commonly used revision control system that does the sort of thing you're asking - at least, not ClearCase or Perforce, which are the other two I've used extensively. I'd say it's a lot more error-prone to do selective tagging correctly than tagging the entire repository. CVS makes it simple to do things another way: * You keep a build workarea where you build and test your product. You can update any single or multiple files you need to fix problems you find during integration and testing. Or branch the files you want to modify. * When you're satisfied that the product built from your build area is release-ready, you tag it from the build area, which automatically tags the versions of the files that you have worked with in that build area. -Original Message- From: Marc Tessier [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 3:13 PM To: Shankar Unni Subject: RE: new feature. I would like to see a feature to extract the most recent revision of a file from a list of TAGs specified as a parameters. Like Tag A B C and the file rev in A is 1.10 and in C it's 1.12 so If a do a checkout or export of TAG A B and C I will get the most recent file that is 1.12 from TAG C. Some people work with CVS by tagging all the files but in my case I just want to work with delta. I do not need to resend to my people all files just need to send them delta so my packages are small all the time. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Shankar Unni Sent: Monday, March 24, 2003 1:33 PM To: 'CVS Mailing List' Subject: RE: new feature. Marc Tessier opined: I would like to know where is the better place to ask new feature to be added to CVS? Is there any mailing list or web page to do so? Well, this is as good a place as any. Would you like to describe the feature you'd like to see? -- Shankar ___ 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 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Minor config help?
Was just wondering - can I define a module in a repository such that it actually comes from a secondary repository? Hmm ... cvs-1/common - cvs-2/common cvs -d:pserver:cvs-1 checkout common such that that checkout actually comes from cvs 2? should I just go RTFM? Jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Fw: Logging Windows code on Linux CVS
- Original Message - From: Jim [EMAIL PROTECTED] To: Riechers, Matthew W [EMAIL PROTECTED] Sent: Monday, February 03, 2003 6:41 PM Subject: Re: Logging Windows code on Linux CVS CVS converts the local system's format to a canonical format on the server and vice versa. If you checkout, edit, and commit all on one platform, you shouldn't see problems with missing or extra EOL characters. You are almost guaranteed to have problems if you mix incompatable platforms between these three steps. No problems until someone mangled the newlines by insertting carriage returns. If you use cygwin cvs, don't use wincvs (or the native windows cvs). Someone made a stupid assumption that removing newlines was a good idea... instead of just maintaining em - heck why not replace tabs with spaces too? -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: use '-d' option
A CVSROOT is defaulted if you're in a tree which you have checked out - the info comes from CVS/Root. If you're outside of any CVS tracked directory you need to specify the root with -d and/or CVSROOT environement variable. - Original Message - From: Kaz Kylheku [EMAIL PROTECTED] To: Monica Li [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 03, 2003 4:01 PM Subject: Re: use '-d' option On Mon, 3 Feb 2003, Monica Li wrote: I imported some files into repository and checked out file for updating. It was all ok last week. Today, when I login I typed: cvs -d :pserver:userName@cvsserver:/repository login Logging in to :pserver:userName@cvsserver:2401/repository CVS password After login, I didn't do anything and logout. The following msg come up: cvs logout: No CVSROOT specified! Please use the `-d' option cvs [logout aborted]: or set the CVSROOT environment variable. You still need a CVSROOT environment variable or -d option, even though you logged in. Logging in just means that a weak security token is deposited into a file in your home directory, which allows you to interact with the repository. The key fact here is that you can log innto more than one repository at a time; the file can contain more than one such token! There is no concept of a ``current CVS repository you are logged into''. The CVSROOT environment variable, the -d option, or, for many commands, the surrounding sandbox (checked out copy) determine what repository you interact with. The cvs logout command too has to know *which* repository you want to log out from. ___ 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: CVS case problem
I've a problem, I have a lot of files with the same name but with different case in the same directory, since I working on UNIX there is not a problem, but now when I tried to check out on NT this return a Conflict and this is fine because cvs try to check out 2 files with the same name but with different content. Yes. You can't do this. There is no workaround. You must either rename some files, abandon Windows, or make a workaround in your own process. Also - make sure your windows editor maintains the case - the windows file systems will actually maintain the case of the filenames (even if it doesn't make them significant), but many(some?) editors will do stupid things like capitalize the filenames before writing it back out. /|/|ike ___ 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
Windows CVS 1.11.4
There's quite a flaw with this CVS. It seems to open ever file as text, and not binary, therefore converting all \n's to \r\n. Even those lines that have \r\n on them.. so files checked out have \r\r\n when they're all done. I use a variety of CVS clients, many are the Cygwin port, which will preserve the \r\n's in the file, and put them in the repository, these, when checked out with the pure windows client are quite mangled... and also, a commit will indicate that ALL the files have changed, when in fact none of them have... this I thought originally wasa date issue... but I think that's not the problem... but then I don't know specifically how CVS decides if a file has changed... But, ya know, unless otherwise specified with an O_BINARY flag, open() on windows opens files in text mode? Jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Hello all, newbie questions re setup
I have been racking my brain on reading documentation on CVS and so I am left with but a few questions. Ok, so, I've installed cvs on two machines. Oh, btw, my questions will be related to the following setup: We want to maintain all of our source code in one central location. Thus I am setting up a server/client model. I have two machines for test purposes thus far. My problem lies in that I am starting this whole thing from scratch and I cannot get a project created on the server. I've got the repository created by using the init command. Let me first show you guys my current setup and what I want to get to and then I will show you what I've done so far. Currently on the server: * installed the cvs binary and friends (/usr/local/bin installation on a Sol 7 box) * created a user called cvs_rep in /u01/home/cvs_rep * performed cvs -d /u01/home/cvs_rep init * decided to use the system password for the authentication model * Added the services line so that inetd could find the proper port. * added the following to the inetd.conf: cvs stream tcp nowait root /usr/local/bin/cvs cvs --allow-root=/u01/home/cvs_rep pserver * HUP'ed the super server and performed netstat -an to make sure that the daemon was listening. It's running and I can login from the client machine. Now this is where I start to get a little fuzzy on what I should do: * Now, I created a directory in /u01/home/cvs_rep called scripts (/u01/home/cvs_rep/scripts). Oh, first, my environment is setup like this: We develop in a few departments as I am sure most companies do. We have Perl scripts, shell scripts, C and C++ src code, and perhaps even some Java code lingering out there somewhere. Each dept has different objectives; for instance, my dept does a lot of development for system applications and management roles. The C and C++ departments do a lot of development for billing type apps. Yet other types of code are written for other business purposes. I will map out what I would *like* to do so that I don't confuse anyone trying to 'splain it... /u01/home/cvs_rep |\ | \ |\ CVSROOT | \ | scripts--- | |\ | | mediation | |\ \ | | traffic__ Perl and SH scripts HERE | |\ \ | | system_ Perl and SH scripts HERE |\ \ | \ `--Perl and SH scripts HERE | src_code- | |\ | | mediation | |\ \ | | traffic_ project_name_ | |\\ \ | | other__ .project_name_ src files and directories |\ \ | .project_name_ src files and directories | \ |src files and directories So, you see, this is where I am absolutely lost. I'd like to do the above as we have about 5 years of stuff that needs to be checked in. The most difficult part of this (besides just setting it up) is actually checking the files in from remote machines. There is a ton of documentation on how to set up a local CVS repository but everything I've read on doing things over the server/client model is somewhat sparse or seems incomplete or not very well explained...at least for my understanding :). For instance, there are some things that you have to do on the server side (I believe) before letting anyone check in a new project, right? I could be wrong. This is the stuff I am having a difficult time figuring out. It can't be that difficult to set something like this up. Im getting caught up in the explanation of things perhaps. Is there a website with a simple reference vs explanations of things? All I need are steps for now. I don't generally care about explainations until after I've played with the actual steps yet. I appreciate any and all assistance and please understand, Im not bagging any documentation in general. I just don't get it yet. - Jim --- Jim Conner | AMA Traffic Systems Analyst USLEC of NC | Security Steering Committee 6801 Morrison Blvd | Unix Systems Development - Perl Charlotte, NC 28211 | wk: 704.319.1222 pgr: 877.317.2448 [EMAIL PROTECTED]| txt: [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Cvs problem
Hi Guys, I'm having a problem with vss2cvs.pl the problem is that when the script tries to concatenate $currdir with $dirline it seems to copy one over the other rather than next to each other. i.e $currfile should be cvsrepository/hi.txt however it ends up being hi.txtository Heres that part of the code: $currfile = $currdir$dirline; open(FILETYPE,ss Filetype \$currfile\ $ssuserpass |); $type = lc(FILETYPE); close(FILETYPE); Does anyone know how to fix this. Please help as I'm only a student in 2nd year at University and have never really used perl or cvs. Thanks, James We can all fly, it's just a definition of how we do it! James McIntosh http://www.geocities.com/mac010382 _ Send and receive Hotmail on your mobile device: http://mobile.msn.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: vss2cvs.pl problem (Was: Cvs problem)
Hi Noel,Yeah I'm on a windows machine(windows 2000 service pack 2) and I am using cygwin too. I have installed Activeperl 5.6 but I was previously using Cygwins perl.I tried chomp before I tried to concatenate the two strings into $currfile but it didn't seem to work as the same error came up. Thanks for your help, James From: Noel Yap <[EMAIL PROTECTED]> To: Jim McIntosh <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: vss2cvs.pl problem (Was: Cvs problem) Date: Thu, 11 Jul 2002 06:57:13 -0700 (PDT) --- Jim McIntosh <[EMAIL PROTECTED]>wrote: I'm having a problem with vss2cvs.pl the problem is that when the script tries to concatenate $currdir with $dirline it seems to copy one over the other rather than next to each other. i.e $currfile should be cvsrepository/hi.txt however it ends up being hi.txtository Heres that part of the code: $currfile = "$currdir$dirline"; open(FILETYPE,"ss Filetype \"$currfile\" $ssuserpass |"); $type = lc(); close(FILETYPE); Does anyone know how to fix this. Please help as I'm only a student in 2nd year at University and have never really used perl or cvs. It looks like the initial (ie on the right-hand-side of the assignment) value of $currdir has a '\r' in it. My guess is that you're on a Windows machine. Is this correct? Are you using Cygwin? If so, are you using Cygwin's perl and are you using a binary-mounted directory? If all you want to do is get this script working, you can do a chop($currdir) before the assignment. I would think, though, that you'll run into other similar problems with the script and even line-ending problems later on with CVS if you are, in fact, running on a text-mounted directory. Noel Join the worlds largest e-mail service with MSN Hotmail. Click Here ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't login cvs!
In article aatm4m$hpe$[EMAIL PROTECTED] Vincent [EMAIL PROTECTED] writes: Hi, I'm trying to setup a cvs (1.10 Halibut) server on a SunOS 5.7 computer. I'm using pserver protocol. I assume that inetd.conf is properly configure as when trying to log in, cvs server ask me for a password. What does the line look like? Is there a --allow-root=/home/cvsroot option on it? Also do have the line in the services file for port 2401? And are you sure that port isn't blocked for any reason? If all of the above are okay then do you have an entry in the CVSROOT/passwd file if the config file has SystemAuth=no? -Jim G. When I try to login (from the server at the moment) using : cvs -d :pserver:myname@mycvsserver:/home/cvsroot login the response is : (Logging in to myname@mycvsserver) CVS password: and cvs seems to wait forever. When I type my password no '*' chars appear. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: can't login cvs!
In article aau7o3$t66$[EMAIL PROTECTED] Vincent [EMAIL PROTECTED] writes: What does the line look like? Is there a --allow-root=/home/cvsroot option on it? Also do have the line in the services file for port 2401? And are you sure that port isn't blocked for any reason? Yes, there is a --allow-root=/home/cvsroot option set, and I think that inetd.conf and services files are well configure because, if I remove inetd.conf corresponding line and if I start a telnet mycvsserver 2401 there is no daemon response else cvs ask me for a password. Sorry, but there's no way that you're telnetting to the port and seeing a password prompt. If all is well then if you typed some text you would normally see something along the lines of : cvs [pserver aborted]: bad auth protocoal start: whateverYouTyped Also, in your earlier post you said: the response is : (Logging in to myname@mycvsserver) CVS password: and cvs seems to wait forever. When I type my password no '*' chars appear. You're never going to see anything, astericks or otherwise, echoed back. Are you sure you're entering the password and hitting a carriage return at the end? (Yes, this is a dumb question, but this sure sounds like the fix is going to be a DOH!) -Jim G. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: why does wincvs show all files as modified
Hi, This is a follow-up to an old thread about WinCVS showing files as locally modified when they haven't been changed in the working copy. We're using WinCVS 1.2 on Windows NT, solely using the CVS client bundled with WinCVS. Our working copies are only managed through the GUI. No command-line checkouts or anything. Shortly after the Daylight Savings Time switch (I'm in the U.S.), I got the all-locally-modified problem that others have described. I checked the timestamps in the CVS/Entries file, and they seemed somewhat strange. Most of them had the correct UTC time, but some seemed to be off by an hour. After doing a status on the directory, these incorrect timestamps all changed by an hour, to the correct UTC time. So I'm experiencing the same daylight-savings timestamp bug already described in this thread. The problem is clearly not the timestamp of the file on disk, nor how WinCVS interprets the timestamps, but the checkout or update that initially sets the CVS/Entries timestamps. The main thing I wanted to point out to the newsgroup is that taking the status of the directory is a very simple workaround, and it's what I've recommended to our developers. You don't have to change the WinCVS installation or blow away your working copy. Whenever I have suspicious locally modified files in WinCVS, the first thing I do is status the directory. Jim Doyle ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Get Hits. Alot of Hits. Really Fast!
Title: FunnelTraffic.com - Webmaster Email Targeted traffic to your website that is FREE. Our pop-behind exit technology supplies your site with targeted hits -- alot of hits. No other internet marketing is more affordable. You can't beat FREE traffic! FunnelTraffic.com Get HITS. Alot of HITS. Really FAST. For This is a one-time emailing. You will not be contacted again. You can contact us at [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Repository file with inexplicable branch revisions
Hi, One of our development groups started up a CVS repository recently and has had some troubles with it, where it looks like the repository has gotten corrupted. I've narrowed it to a single repository file, which has headers that look like: head1.1.1; access; symbols production:1.1.1 ISO:1.1.1; locks; strict; comment @# @; 1.1.1 date2001.11.05.21.08.47;author rslate; state Exp; branches; next; desc @@ 1.1.1 log @Initial entry There are no obvious glitches as a result of direct edits, like missing lines or added characters, but the revision history is extremely odd. There is only one revision, called 1.1.1! The file was originally added to the repository via an import command like cvs import ncpc ISO production. Normally the revisions would be 1.1.1.1 and 1.1, with the vendor branch tag on 1.1.1. The effect on the CVS client/server is that the module cannot be checked out, with the error bad branch tag in checkout, which sounds only reasonable given the strange revisions. It appears that the strange revision state must have been caused by a sequence of legitimate CVS commands, but I've been trying to reproduce it by moving tags, deleting tags, outdating revisions, and committing with explicit revisions, and I haven't gotten anywhere. The repository is under CVS 1.11.1p1 running as pserver on a Unix box. Can anyone think of a sequence of CVS commands that would result in this case, with the only revision having a branch number like 1.1.1? At this point the best we can do is remove the repository file from the server and re-add it (since it's been corrupted since the very day it was added). But I want to find out what operations to warn people against, or what I can do to protect the repository from these operations. Thanks in advance, Jim Doyle [EMAIL PROTECTED] ncpc.sps,v ncpc.sps,v Description: Binary data
RE: How to get log messages *after* one tag up to another tag
Is there a chance the cvs log features recently added can be further extended to work across branches? To a user, I think 1.3, 1.3.2.1, 1.3.2.2, ... looks like a legal sequence that cvs log should be able to follow. Would it make sense to allow ranges A::B, where A precedes B on the same branch, *or* A::B' is itself a legal range, where B' is the origin of the branch B is on? [snip] It's also not quite as simple as it might seem, since I believe that 1.2:4.5.6.7.8.9 should also be a valid range, no? (All revisions with a single dot are on the trunk, reguardless of the major revision number; on other branches, the major componenents of the revision number must be exactly equal.) Larry, Thanks for the reply. I see your point about the trunk major revisions - I thought there might be additional complications I wasn't seeing. And yes, the kind of general functionality I would hope for would support 1.2:4.5.6.7.8.9 as a valid range. Would this really complicate the code, though? I haven't looked at the source much, but I have seen that there seem to be functions for getting the origin of a branch (RCS_getbranch? or RCS_whatbranch?). As long as you can jump from a branch revision to the branch origin, and get from a revision to the one that precedes it within a branch, it looks like listing the revisions wouldn't be too bad. To take the example above, 1.2:4.5.6.7.8.9, I'd imagine the code: * starting with 4.5.6.7.8.9 * decrementing the minor revision number until it gets to the first branch revision 4.5.6.7.8.1 * jumping to the origin 4.5.6.7 of the branch 4.5.6.7.0.8 * decrementing the minor revision again until 4.5.6.1 * jumping to the origin 4.5 * tracing revisions backwards along the trunk, decrementing the minor and major revisions, until it gets to 1.2 * Do the necessary primitives (getbranch, etc.) exist to support an algorithm like this? Would an algorithm like this really cover all the bases? Would it be possible to confine these code changes to the log command, or would it affect other parts of the source? Jim [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: How to get log messages *after* one tag up to another tag
Now, I need a list of all changes made after rel_5_0_1 up to the rel_5_0_2 tag, i.e. all changes added in release 5.0.2. If you get the current development release of CVS from www.cvshome.org you can do that with: cvs log -r rel_5_0_1::rel_5_0_2 I started using the current development release of CVS to get the revision range log feature mentioned above, and I've been very happy with how it works on the trunk of a simple example, but I've run into a stumbling block when applying it to a repository with a branch. It looks as though the revision range can't run from the trunk to a branch off the trunk. Let's say rel_5_0_1 tags revision 1.3 on the trunk, and rel_5_0_2 tags revision 1.3.2.1 - in this case, CVS complains about the range -rrel_5_0_1::rel_5_0_2 and selects no revisions. Is there a chance the cvs log features recently added can be further extended to work across branches? To a user, I think 1.3, 1.3.2.1, 1.3.2.2, ... looks like a legal sequence that cvs log should be able to follow. Would it make sense to allow ranges A::B, where A precedes B on the same branch, *or* A::B' is itself a legal range, where B' is the origin of the branch B is on? Then the code could walk backwards from B, jumping to the branch origin of B while A has fewer numdots than B. Does this make sense when coming at it from the point of view of implementing CVS? I think this is a really common and simple case that people will run into again and again when reporting log messages. It's pretty common to release a version of your product and create a branch to handle bugfixes to that version, and if you want ChangeLogs for the changes between bugfix releases on that branch, you're going to need cvs log -rtag1::tag2 to work from the trunk to the branch. This makes sense to me; does it make sense to other CVS users? Here's a more detailed example of the desired behavior at work: 1. Start with a module, examples, with two files, bar.java and foo.java, at revisions 1.1 and 1.2, respectively. 2. Tag with release_1_0. 3. Create branch tag release_1_0_bugfixes from regular tag release_1_0. 4. Checkout branch. 5. Change and commit bar.java to create branch revision 1.1.2.1. 6. Tag branch with release_1_0_bugfix1. 7. Change and commit foo.java to create branch revision 1.2.2.1. 8. Tag branch with release_1_0_bugfix2. 9. Try to get log messages for revisions between release_1_0 and release_1_0_bugfix1: cvs log -rrelease_1_0::release_1_0_bugfix1. The user needs the log message for revision 1.1.2.1 of bar.java. But no revisions are selected: cvs log: invalid branch or revision pair release_1_0:release_1_0_bugfix1 in `/home/jim/repository/examples/bar.java,v'. 10. Try to get log messages for revisions between release_1_0_bugfix1 and release_bugfix2: cvs log -rrelease_1_0_bugfix1::release_1_0_bugfix2. The user needs the log message for revision 1.2.2.1 of foo.java. But no revisions are selected: cvs log: invalid branch or revision pair release_1_0_bugfix1:release_1_0_bugfix2 in `/home/jim/repository/examples/foo.java,v'. I really appreciate any comments. I'd like to know if this feature might get implemented in CVS, or if I should bother working on a patch myself, or if I need to just create some workaround outside of CVS. Thanks, Jim Doyle [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
(no subject)
hi, How can i make modulelist in the file name modules on server? The file on my server has no info about module. Jim.Wang ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
(no subject)
How can i import a project in another directory to server when i am in current directory ? Jim.Wang ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Web developpement with CVS...
[EMAIL PROTECTED] wrote: Hi, We are trying to install CVS on one of our server. Right now, it's up and running and works pretty fine. It runs on a Linux box and we can connect to it with WinCvs on our Win2000 workstations. The problem is simple : we do web developpement, which means the latest version of the files should always be present on the server, not only in the cvs repository. I would have them set it up in sandboxes. If you are using Apache as the web server this is simple to do with virtual hosts each pointing to a different dir. Or you could do it with just using public_html dirs that are also samba export so they can get to them via Windows. Checkout into that dir and then they can edit. With virtual domains they would be able to check it before the commit. That way you don't get seriously broken code in CVS. Hope all this makes some sense. The syncing part is different I don't know if you want your web site syncing to head all the time. You may be better off syncing it to a tag like QA or something that way you know the code is good. Then write a little script to do the cvs update and put it in cron for every hour or something like that via ssh. This is probably not exactly technically correct but should get you in the ball park for syncing. You would need to set up keys for the user with ssh. Something like this: #/bin/sh CVSROOT=username@host:/path/to/cvsroot CVS_RSH=ssh WEBDIR=/path/to/htdocs LOGFILE=update.log DATE=`date +%m%d%h # Move the logfile. mv $LOGFILE $LOGFILE.$DATE cd $WEBDIR # Create a tag so you can roll back. cvs rtag -r QA WEB_SITE_$DATE # Update the site to the latest tag. cvs update -r WEB_SITE_$DATE modulename update.log # if you want to get fancy you could do a mail # everytime it does this and attach the logfile. jim Let me explain myself : Suppose we're working on a project with some PHP, I don't want to install PHP on every programmer's workstations... I'd like them to simply checkout their stuff...do their changes..commit it and than check (via their web browser) on the server to see if it's right... What is the best way to do this ? Is there any way to ask CVS to copy the changed file at the right place, and this, at each commit ? Since we host sites both on Linux and Win2000, will cvs even be able to copy the files over the network to another web server ? Thanks a lot people... I hope this is not too stoopid :) Regards, Jonathan Kemp Internet Services Manager Capella Technologies ___ 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
Fwd: Re: pvcs to cvs and magic branches
Basically, my changes to the script fixed the part that was breaking on my archives, but the changes broke other parts (including this one.) I can fix it OK, but I hate working on code whose purpose I don't understand. Thanks for the replys, Jim But then, why expend all this extra effort to do something counter to CVS's documented design, just because you ought to be able to get away with it? The conversion script already makes sure the branch numbers are even; why not just go with the flow? -- | | /\ | |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | | / With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. - RFC 1925 (quoting an unnamed source) ___ 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
pvcs to cvs and magic branches
I'm in the process of converting a project from pvcs to cvs. I found the
pvcs2cvs.pl script, which basically extracts each rev from pvcs and then
checks it into rcs. I'm tweaking the script to handle some cases the original
author didn't expect, and I'm very curious about a section of
the script that deals with converting pvcs revs to rcs revs (the subroutine is
at the end of this message.)
What is the reasoning for multiplying all branch revs by 2? RCS doesn't
require this. I thought that cvs could read rcs archives without a
problem.
Thanks,
Jim
sub pvcs_to_rcs_rev_number
{
my($input, $num_fields, @rev_string, $return_rev_num, $i);
$input = $_[0];
$_ = $input;
$num_fields = split /\./;
@rev_string = @_;
# @rev_string[$num_fields-1] += 1;
for( $i = 1; $i $num_fields; $i += 1 )
{
if ( $i % 2 )
{
# DRP: 10/1
# RCS does not allow revision zero
$rev_string[ $i ] += 1;
}
elsif ( $i )
{
# DRP: 10/1
# Branches must have even references for compatibility
# with CVS's magic branch numbers.
# (Indexes 2, 4, 6...)
$rev_string[ $i ] *= 2;
}
}
# If this is a branch revision # (PVCS: a.b.c.*) then we want the CVS
# revision # instead. It's okay to do this conversion here since we
# never commit to branches. We'll only get a PVCS revision # in that
# form when looking through the revision labels.
if ($input =~ /\*$/)
{
pop @rev_string;
push @rev_string, splice (@rev_string, -1, 1, 0);
}
$return_rev_num = join ., @rev_string;
return $return_rev_num;
}
Get free email and a permanent address at http://www.amexmail.com/?A=1
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
RE: LockDir
Unless this has changes recently, I would add a caveat that if you use
softlinks to directories in your repository, you are in some danger because
the links are not replicated in the LockDir, thus locks are not necessarily
created in the directory containing the history files.
-- JimLane
-Original Message-
From: Derek R. Price [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 11, 2001 2:35 PM
To: KOIE Hidetaka
Cc: [EMAIL PROTECTED]
Subject: Re: LockDir
I didn't apply this:
KOIE Hidetaka wrote:
In doc/ChangeLog,
2001-06-08 Larry Jones [EMAIL PROTECTED]
* cvs.texinfo (config): Mention using LockDir on in-memory
filesystem to speed up locking.
In doc/cvs.texinfo,
It can also be used to put the locks on a very fast
in-memory file system to speed up locking and unlocking
the repository.
You need to create @var{directory}, but
sc{cvs} will create subdirectories of @var{directory} as it
needs them. For information on @sc{cvs} locks, see
@ref{Concurrency}.
I comment:
Take care owner and permissions of @var{directory} and
@var{directory}@file{/..} as same as CVSROOT.
This is already covered by (from cvs.texinfo):
Put @sc{cvs} lock files in @var{directory} rather than
directly in the repository. This is useful if you want
to let users read from the repository while giving them
write access only to @var{directory}, not to the
repository.
If using in-memory file system, it is volatile during reboot,
don't forget to create @var{directory} in a startup script like
/etc/rc.
This seems better to leave to the filesystem docs. Not only should any user
capable of setting up an in-memory filesystem be capable of solving this
problem on their own after at most a single reboot, but I can conceive of a
disk-backed in-memory filesystem that doesn't have this requirement.
Feel free to argue the point, of course, but I think I will wait until the
question comes up a few more times on this list to move the answer to the
FAQ
and maybe later to the Cederqvist.
Derek
--
Derek Price CVS Solutions Architect (
http://CVSHome.org )
mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net )
--
... one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of their C
programs.
- Robert Firth
___
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: Use of CVS on large scales
I think there are probably more one issue here. The market that ClearCase is for and the market that CVS is used for a two different things. ClearCase is a process-based SCM system and CVS is not. By process-based, I mean that the processes are internal to the system. Unlike a CVS or Perforce which the process is defined by the Configuration Manager and everyone is expected to follow that process. ClearCase does the process part for you. Which for a growing company incurs a lot of admin time. CVS on the other hand can be flexible. As a process is improved you can tweak CVS and your automation to fit the need with little changes. In AntiPatterns and Patterns in Software Configuration Management by Brown, i McCormick, and Thomas, the first Antipattern is the Silver Bullet. This AntiPattern, is based on the fact that no CM tool ever does the job completely. It is more of a fit for your organization. CVS may work now but maybe will not work as good in the future. If he's a Quality person. He may insist on information like file relations, and stuff that may not be as easy to get out of CVS as a ClearCase. I know my boss did, but it was a matter of writing a Perl sript to get the information in the display format that he wanted. He may also not realize that, the bug tracking system, Bugzilla operates with CVS. That could be what he's looking for. A lot of the commercial bug tracking software works with Clear Case. I've looked at most of the commercial products and I like Bugzilla and most of the mozilla tools. We use CVS at Jabber.com. For web site and software development. And I have implemented automated build scripts, auditing control and testing, and even some automated software tests. Hope some of this helps. jim On Fri, Jun 08, 2001 at 11:40:35AM +1000, Lucas Chan wrote: Guys, We are currently looking at implementing some kind of version control system. We have been trialling CVS for the past few weeks, storing sources on a FreeBSD machine and using WinCVS on our development machines. It seems that this is exactly what we're looking for. I have struck a problem that I'm hoping some of you can help me with. Our company hired a testing expert a week or so ago, and he is currently opposing our move to roll out WinCVS. This is because: a) He's never heard of it. b) He doubts that it is scalable enough for us. c) He believes that anything that's free _must_ have disadvantages (as opposed to Clearcase for example). This didn't go down too well with me (or my team) because: a) For someone who's supposed to be an expert on testing systems, it surprises me that he's never heard of CVS. b) When talking about scalability, I gave the example that FreeBSD itself is maintained using CVS. i.e. implying that we're only building web sites, not whole operating systems. This didn't seem to be good enough evidence for him. c) And of course, I'm a FreeBSD and Open Source fan. So, to cut to the chase... it would be great if some of you could show me where to find further information about CVS. I'm particularly interested in it's uses for (really)large scale projects, perhaps even some stats on the quantity of sources it can maintain, any advantages it has over commercial source control products, etc. I've checked out the CVS web site but none of the information there was useful in this context. Something like... a case study of a large software company using CVS would be pefect (I imagine). Thanks for your time everyone. Regards, [ lucas ] [ the ego has landed ] ___ 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: Crazy idea - replace RCS backend with ClearCase...!!!
I got to be pretty good at Clearcase and miss the hell out of it. I loved CVS, but CC is a much better system. The drawbacks to CC are: 1) Huge learning curve. But well worth it. 2) Expensive. But if you've already got it, use it. 3) Takes lots of disk space. Sounds like you've already taken care of that. 4) Very CPU/Network intensive, especially Clearmake. It took a lot of money and a couple of dual-CPU Suns to make it acceptable, but it was nowhere near as fast as regular make. IMHO, you should maintain your projects under CC as you've already got it. To keep your CVS repository up-to-date just treat the sources as vendor code and import it into the repository once in a while. If non-CC folks are updating your repository as well then it's a simple matter to let CC merge those changes into your VOB. In the beginning we did try to make CC look more like CVS/RCS, but once we got good with CC we realized how silly an idea that was. jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS and Solaris 8.x For Intel
Hi, I am new to CVS. I just downloaded Solaris 8.x (for intel x86) from Sun for our server. Which version of CVS do I need? I only see Solaris for Sparc, not intel x86. Thank you, Jim Urban Project Manager Netsteps Inc. winmail.dat
Multiple projects, or multiple repositories
Assuming you're going to use CVS for several projects in your network, is it better to have 1 repository with multiple projects, or multiple repositories containing a single project? I don't mean project in the CVS sense, I mean it in the customer-signed-a-contract sense. Projects tend to overlap a bit. Most are based on a linux kernel, most have custom device drivers. They also differ in some significant ways. We have multiple Linux kernel version, different CPUs (StrongARM, SH4, Celeron, etc). jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
tagging files via script
I have a script that tags files based on an existing tag. I use it to be selective in what gets into the next release. Currently I use rtag and pick up all files with the existing tag in a particular directory. What I want to do is be able to selectively re-tag specific files. I know that tag will allow you to tag specific files, but it requires the CVS directories in the local directory and rtag only works with directories. I know I can do this with RCS.is there anything I should be aware of before I start using RCS to tag the specific files? Does CVS rtag to anything radically different? I'm still on 1.10 of CVS, but plan to upgrade soon. Any thoughts/suggestions? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: looking for cvs, cvsweb info for hurd.gnu.org
Many thanks all for the help and links Jim ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
