[cvsnt] Re: Bad upgrade experience to current CVSNT 2.50.3 (2260)

Tony Hoyle tony.hoyle at march-hare.com
Fri Mar 24 17:43:39 GMT 2006

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

John Peacock wrote:
> 1) The installer does not include a required DLL (dbghlp.dll) and there 
> is no mention I can find on the CVSNT website regarding where to get it. 

Yes it does - it's a mandatory part of the install (it's dbghelp.dll).

> 2) My postcommit hook failed to run; after correcting the backslash to 
> forwardslash issue, all I would get was "Script failed" and nothing 
> else.  It turns out that I had to prepend "perl" to my postcommit script 
> line because how CVSNT is executing this no longer uses the CMD mapping 
> between .PL files and the Perl executable.

This never worked anyway due to a bug in perl (it couldn't read stdin 
when passed in that way).

> 3) The "shadow" feature either doesn't work as advertised or the 
> documentation does not reflect reality.  A simple line like this:
> ^websites/Home HEAD W:/websites/Home

Is W: a network drive?  Not using network drives has been repeated so 
many times I've lost count...

This feature works - I use it regularly as do many others.

> 4) Whoever decided that "postcommand" is a suitable replacement for 
> "postcommit" never tried to use it to update a checked out copy. 

1. You can still use postcommit
2. The shadow file is there for checked out copies
3. It's working as advertised.  What did you expect to happen?  Your 
script should be checking the command that is passed for commit or 
anything else that you're interested in (commonly tag, which postcommit 
didn't trigger on).


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook