top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

cvs diff within verifymsg

0 votes

I have a verifymsg script that runs the changed source code hunks through a series of checks, exiting with an error if any of those checks fail. In order to determine what has been changed, the verifymsg script
runs "cvs diff" (without any filename arguments) and parses that output.

I'm aware that locking is already enabled by the time verifymsg is run. However, if a plain "cvs commit" or "cvs commit -m 'message'" is run, the diff works fine without any errors or warnings. If instead "cvs
commit file.c" is run (even if file.c was the same file that would have been implicitly checked in by the plain "cvs commit"), the whole thing deadlocks with the usual message:

cvs diff: [00:32:20] waiting for username's lock in /path/to/repo/module

I'm not surprised by this, but I am surprised that it works when no explicit filenames are given to commit.

More to the point, how can I circumvent the locking for this use case so I can get cvs diff output in verifymsg?

posted Jun 18, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes
Best answer

Use cvs -n diff.

answer Jun 18, 2013 by anonymous
Similar Questions
+1 vote

We have stuck in integrating CVS with Bugzilla. We tried some online documents i.e. CVS Zilla, which we are unable to download it.

Is there any step by step document which we can follow?

+4 votes

I want to configure CVS on linux machine to maintain history and revision of files.

+3 votes

I am planning to use CVS for one of my project and would like to understand the system/hardware requirement for below project requirement:

 * Estimated no. of CVS users: 5
 * Project size: 100 MB

What would be that optimal hardware requirement in terms of:

 * Processes
 * RAM
 * Hard disk
+1 vote

I'm facing to a strange problem: cvs corrupts rcs file while I'm trying to tag it. The file itself is about 50Mb (and it's binary) and rcs file is about 2.1G.

Every time I launch

 cvs rtag -B -a -F -r 1.526 -b "my_tag" project/file.bin

rcs file turns from 2.1G into 110K file with completely lost history and file itself. All other operations (commit, update, etc) works fine. This is the biggest file in repository and the only file with such behavior on tags. Others are working fine.