[cvsnt] Latest updates - cvsnt 2.5.01 build 1990

[Bo Berglund]

If you can successfully perform the commit using the command line
cvs then I suggest this is a problem with WinCvs rather than cvsnt.
In that case your best bet might be to ask on the cvsgui list instead.

/Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Gary Brunton
Sent: den 7 juni 2005 08:37
To: cvsnt at cvsnt.org
Subject: [cvsnt] Latest updates - cvsnt 2.5.01 build 1990


>Ticket  Description
>#22     Handle negative return from verifymsg

My verifymsg batch file works perfect now! It now correctly stops a
commit if the file exits with a 1:)

Everything is working perfect except for one thing. My client is
hanging after a succesfull commit.

Again, I using cvsnt 2.5.01 build 1990, windows xp, WinCVS 2.0.0.2.  I
have two scripts that are running. I've updated the following files to
point to my scripts:

checkoutlist
c:/gary/cvs/cvsrepo/southwestservicetpa/CVSROOT/bugzillaIntegration.pl
c:/gary/cvs/cvsrepo/southwestservicetpa/CVSROOT/bugVerification.pl

verifymsg
DEFAULT perl c:/gary/cvs/cvsrepo/southwestservicetpa/CVSROOT/bugVerification.pl
$USER

loginfo
DEFAULT perl c:/gary/cvs/cvsrepo/southwestservicetpa/CVSROOT/bugzillaIntegration.pl
$USER %{sVv}


Scripts run perfectly now. The only problem is that when everything
works WinCVS just hangs there. I have to force a stop by pressing the
"Stop CVS command" at which point I get the following message: cvs.exe
[commit aborted]: received interrupt signal

In WinCVS the file I was commiting is still red (as if it was not
committed) but if I do an update on it it changes to white and cvs
exits with a code of 0. Which tells me it did succeed with the commit.

I'm not sure what is going on here. Does anyone have any suggestions?

Thanks,
Gary
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt