Can I use CVSNT to replace Visual SourceSafe, PVCS, ClearCase or Perforce?

CVSNT is not an emulator designed to replace any of them. However these tools solve problems generally defined by the phrases "version control" and "configuration management", and those are the same problems that CVSNT is designed to solve. Therefore in some situations it may be possible to switch one for the other and have very little impact on your business.

Several scripts are available for converting the core repositories of some versioning systems such as Visual SourceSafe to a CVSNT repository. March Hare Software can also provide consulting and training to assist with this.

Can I use CVSNT to replace CVS?

CVSNT Server and command line client are available for free download pre-compiled for the following platforms:

• Windows
• Mac OS X 10.3.7
• Solaris 9
• HPUX 11i
• Red Hat ES Linux v4

Why are there advertising messages in the commit messages (and how to remove them)

There is a discreet advertising message added to every commit from a windows CVSNT client or on a windows CVSNT Server to encourage more users to invest in supporting the CVSNT development effort (either by joining the newsgroup, contributing code/tests, or by contributing to the cost of paying development staff). Our goal is to add two additional full-time programmers and we believe we can achieve this if at least 1% of those that download CVSNT purchase at least 1 license of CVS Suite.

• The advertising messages can be removed from the commit log history using the admin command
• You can prevent the client putting the advertising in the message by using cvs commit -M "message" as described in Bug 5397.
• You can prevent the server putting the advertising in the commit message by setting HKLM/Software/cvsnt/PServer, "HaveBoughtSuite"="yes" as described in bug 5398.

The editions of the CVSNT software purchased from our web site (CVS Suite etc) do NOT include the advertising.

If you purchase CVS Suite from our web site and upgrade your client and server then previous advertising messages stored in the repository will be hidden from the output of cvs log etc, Existing commits with the advertising are not automatically altered by the purchased CVS Suite software only hidden so that it can no longer be seen.

It has already been drawn to our attention that some companies may want purchase a single license to assist the project but not license ALL their users, however our store does not currently offer such a product but may be updated to include this in the future.

All customers who purchase CVS Suite 2008 also receive access to a build of CVSNT 2.5.04 that hides previous advertising messages and does not create new ones.

The CVS Suite software currently for sale from the web site includes many features not present in CVSNT and so is licensed per person (ie: if you have 20 people accessing the server you should purchase 20 copies of CVS Suite).

CVS Suite also includes many bug fixes, a complete list of the 380+ changes between CVS Suite 2.5.03 and CVS Suite 2008 is available here.

On WinCVS I get "remote server does not support the ls command" errors

Reports of malware or a virus in CVSNT

The heuristics problem is typically resolved within a few days of it being reported. Other popular anti-virus products (for example, McAfee VirusScan and Norton AntiVirus) do not exhibit this behavior and may be used to confirm that the product you have downloaded is free of viruses.

You can compare the results from different anti-virus products by uploading a file here:
http://www.virustotal.com/

NOTE¹: March Hare Software do not have any affiliation with virustotal.com

NOTE²: The signed downloads of CVSNT, EVS, CVS Suite and CM Suite that March Hare Software provide from march-hare.com do not include malware or viruses.

I have set up an ACL but non authorised users can still check out files

The cvsnt command chacl is used to create an access control list (ACL). It is documented in the manual here.

An access control list is defined on a directory and branch (or trunk) to restrict read, write, create, tag and control by users or groups. The access modes are documented in the manual here.

Users and groups are synonymous - you can either specify permissions for individuals or groups. The user and group names used will depend on the authentication mechanism being used. Most CVSNT users authenticate against an Active Directory (windows) in which case the user and group names are the same as your windows login.

You can also use the lsacl or rlsacl commands to list the current permissions.

Owners (creators) automatically have administrative rights on any object they create.

The ACL system has two basic modes of operation:

• Allow all access by default
• Deny all access by default

CVSNT access control (and all other access control systems) are designed to work primarily on directories. Do not store a file in a "public" directory and try and use ACLs to completely hide it from all non-authorised users, store it in a separate (or a sub) directory and set the access control on that directory.

Location of TortoiseCVS.org FAQ

XP Home always logs in a "Guest" (Simple File Sharing)

On XP Home the only workaround is to explicitly specify the username in the CVSROOT string, which will override the default. On XP Pro it is strongly recommended to disable "Simple File Sharing" (commonly known as "Broken File Sharing").

Checking out to a remote samba share fails

• They have not downloaded and installed the CVSNT on the actual client and are using a remote share or a samba share as a workaround. This is typically done from a Unix server to checkout to a Windows PC or vice versa.
• The user wants to store the working files / sandbox on their "home drive". This is typically done from a Windows PC.
• Several users want to share a sandbox

Support for sandboxes on remote shares is available with Professional Support (not CVS Suite support).

If you do not have professional support then storing sandboxes on remote shares is not supported. Use a Unix client on the remote machine to checkout the sandbox, or use a local drive on the Windows machine.

Error reading from server <whatever>: -1: Unknown error

The usual cause for this is Antivirus and/or "Personal" firewalls, which can break Handle Inheritance. To verify the culprit uninstall all such programs from your machine and try again (simply disabling them is usually not enough). If it then works re-install the software until you find which one is causing the breakage (then file a bug with the vendor concerned).

If all else fails try WinsockXPFix which restores the TCP/IP stack to a working state after spyware/AV/firewalls cause problems.

In particular the Nod32 av exhibits this behaviour. The current workaround is to disable the "IMON" service and reboot. Eset have been contacted about this problem. Until it is fixed it is recommended that Nod32 is not used on a machine running cvsnt.

Also known to break the stack is Aventail AutoSocks. No known workaround other than to uninstall it.

Cant authenticate - server and client cannot agree on an authentication scheme (got "")

[80090311] No authority could be contacted for authentication.

The SSPI protocol authenticates the client against the Windows Domain Controller or Active Directory. Microsoft have various security strengths for performing this authentication including NTLM, NTLMv2 and Kerberos.

CVSNT 2.5.02 clients will use the highest possible authentication security strength with the SSPI protocol - this is usually Kerberos. However CVSNT clients released prior to 2.5.02 generally used NTLM to authenticate with the server. CVSNT Servers prior to 2.0.51d can incorrectly respond that they support Kerberos when they do not. In this case the newer client will insist on using Kerberos and the connection fails with the message [80090311] No authority could be contacted for authentication.

The solutions are:

• Upgrade CVSNT Server to a stable version more recent than 2.0.51d
• Downgrade the CVSNT Client to a version older than 2.5.02
• Change the CVSROOT to :sspi;force=NTLM:user@host:/repo . In this case you will have to re-create your sandboxes or use a WinCVS macro to change the CVSROOT embedded in the workspace.

Connect using SSH "Unable to authenticate Couldnt connect to remote server - plink errorcvs"

Access denied FATAL ERROR: Unable to authenticate Couldnt connect to remote server - plink errorcvs

This is caused by a password failure. Use cvs logout then cvs login to correct the problem. For a more secure solution use the CVSNT Password Agent to store your password in memory rather than in the Windows registry or .cvspass file (unix).

Cannot connect using SSH, password prompt does not include username

cvs -d :ssh:user@host:/reponame ls
@host’s password:
Access denied

This is caused by interaction between CVSNT and PUTTY and occurs when you have a saved PUTTY session with the same name as the HOST. Alter the name of the saved PUTTY session to resolve this error.

Why does CVSNT attempt to contact 69.93.197.231

How is the TortoiseCVS included with CVS Suite different from the standard "free" version?

• Browse server for checkout of module or single file
• Edit dialog (must be enabled in preferences)
• Defect number integration on Edit, Commit and Merge
• Additional Preferences
  • Read only files on checkout regardless of watch state
  • Set ACL on edit for working with shared sandboxes
  • Edit dialog preferences
  • Disable looking for Modules file (not requried for CVSNT)
  • Eclusive editing options
  • CVS Server setting (for use with SSH)
• Improved context menu handling
• Show bug numbers in revision graph and log
• Support for CVSNT SSH secure authentication
• Is tested with the other components of CVS Suite
• Behaviour is consistent with the documentation included in CVS Suite
• Is supported by March Hare Software

Are the commercial releases of CVS Suite the same as the free CVSNT?

The changes in the community editions of CVSNT are driven by the requirements of the open source developers, whereas the changes in the CVS Suite are driven by our customers. Features only available in CVS Suite include:

• CVS Suite High Performance Server Service
• Bugzilla, Mantis and Atlassian Jira Integration
• Multi-Site unison synchronisation
• Visual Studio Integration (SCCI)
• CVS Suite Studio - Graphical CVS Client
• Release Manager
• Install Guide / eBook
• Using CVS Suite with Eclipse guide
• Using CVS Suite with SQL Navigator and Oracle Guide

Generally this CVSNT Community Edition supports newer versions of Open Source Linux libraries and has cutting edge experimental features, and the CVS Suite works with and is tested with Commercial Linux, Windows and Unix distributions and is more stable and has features commercial software developers require.

Between CVSNT 2.0.51 and CVSNT 2.5.02 we did try and keep the two releases very similar - however from CVSNT 2.5.03 it became clear that the community of open source developers wanted to use much newer technologies (like libxml2 versus expat) than most commercial operating systems supported.

The source code for all versions of CVSNT are available from the CVSNT repository, and all builds are available at some time from the open source web site. However the open source CVSNT web site only keeps one build of CVSNT available at any time. Open source developers can "checkout" any version from the repository and build it at any time.

March Hare Software provide five levels of commercial support, and all levels have access to the latest software at the time of purchase.

Silver, Gold and Platinum Annual Software Maintenance and Support customers have access to the entire history of stable and patched releases of CVS Suite.

CVS Suite (no Annual Software Maintenance and Support) customers have access to the latest stable and patched versions at the time of purchase.

All Annual Software Maintenance and Support customers receive patched versions of CVSNT as frequently as every fortnight (but not usually so - since there are many fortnights with no bugs reported).

All CVS Suite customers also receive some plugins and client applications which are not licensed under the GPL and are not available for free. The source code for these is not available in the CVSNT repository.

Conversely not all versions of CVSNT are made available to professional and basic support customers. Releases of CVSNT made to customers undergo additional quality assurance and release procedures.

The following data was generated using David A. Wheelers SLOCCount:

• TOTAL SUITE CODE: 794,361 lines
• DIRECTLY FROM CVSNT PROJECT: 443,003 (56%) lines
• AVAILABLE IN SUITE ONLY (NON-GPL): 35,324 (4%) lines

Low Performance CVSNT versus High Performance CVS Suite

The commercial implementation is faster but also uses a manager process that is not open source. This provides:

• reduced lag on client performance while servers start
• allows the server processes to share information to improve performance

It is not possible to use CVSNT 2.8 Server without the manager process.

How much of the code is Free/Open Source

Therefore to help them we make a deliberate decision to keep a small but extremely useful part of the code non-open source.

We have NOT removed any features or documentation from the Community edition of CVSNT, but included in the CVS Suite these additional components:

• CVS Suite High Performance Server Service
• Bugzilla, Mantis and Atlassian Jira Integration
• Multi-Site unison synchronisation
• Visual Studio Integration (SCCI)
• CVS Suite Studio - Graphical CVS Client
• Release Manager
• Install Guide / eBook
• Using CVS Suite with Eclipse guide
• Using CVS Suite with SQL Navigator and Oracle Guide

NOTE: The majority of code in the CVSNT Project is Copyright March Hare Software Ltd, with some code Copyright March Hare Software Ltd and Tony Hoyle.

The following data was generated using David A. Wheelers SLOCCount and CVS Suite 2009:

• TOTAL SUITE CODE: 794,361 lines
• CVSNT PROJECT: 443,003 (56%) lines
• AVAILABLE IN SUITE ONLY (NON-GPL): 35,324 (4%) lines

CVSNT ONLY

• ansic: 224603 (55.09%)
• cpp: 123608 (30.32%)
• sh: 48791 (11.97%)
• asm: 3495 (0.86%)
• ada: 1681 (0.41%)
• perl: 1493 (0.37%)
• pascal: 1089 (0.27%)
• cs: 1008 (0.25%)
• python: 918 (0.23%)
• yacc: 805 (0.20%)
• sed: 181 (0.04%)
• lisp: 7 (0.00%)
• Total Physical Source Lines of Code (SLOC) = 407,679

cvsnt + winmerge + tortoisecvs + wincvs:

• cpp: 436878 (57.56%)
• ansic: 255095 (33.61%)
• sh: 50251 (6.62%)
• asm: 5570 (0.73%)
• perl: 2234 (0.29%)
• cs: 1887 (0.25%)
• ada: 1681 (0.22%)
• yacc: 1559 (0.21%)
• pascal: 1289 (0.17%)
• python: 962 (0.13%)
• php: 726 (0.10%)
• exp: 692 (0.09%)
• sed: 181 (0.02%)
• ruby: 25 (0.00%)
• lisp: 7 (0.00%)
• Total Physical Source Lines of Code (SLOC) = 759,037

COMMERCIAL SUITE CODE ONLY:

• cpp: 26524 (75.09%)
• sh: 8800 (24.91%)
• Total Physical Source Lines of Code (SLOC) = 35,324