When attempting to import a code control group to the CVS database. I get the following error message:
Error in CVS (while attempting to get file list for project '<name>'): Missing CVS\Entries file for folder ....\local_repository\<name>.
TOAD determines which files and folders are in your repository by reading the file named Entries. This normally resides in a folder named under each of your working folders. If TOAD cannot find this file in any of your working folders, you receive the \Entries file error.
This can happen in one of two ways:
- If you have not yet performed a cvs co . to check out everything, your Entries and Repository files will not have been created automatically. This can be remedied by performing the cvs co . (remember to include the dot in the command).
- Some versions of CVS will not automatically create a CVS\Entries file in the root working folder. This does not affect normal CVS operation, but it does prevent TOAD's CVS support from working.
To manually correct the problem causing a CVS/Entries file error
1. In your root working folder, create a new folder named CVS.
2. In the new CVS folder, create an empty file named Entries.
3. In the new CVS folder, create file a named Repository containing a single line with the single character . (the period) followed by a carriage return.
4. Log in to CVS.
5. In your root working folder, execute the CVS command: cvs co .
6. In your root working folder, execute the CVS command: cvs update .
Note: You may need to perform the "update" on individual files or projects instead of the whole repository.
Setting up your Entries file
Once created, you can set your Entries file to check out the files you want. You can check out the entire repository, or only a few projects.
To check out your entire repository
- Leave the Entries file empty to check out the entire repository.
To check out a few projects in your repository
1. To keep only a few projects in the repository, enter the projects in your Entries file as described below:
Where Projectn is the name of the project.
2. Check out and update each project one by one. For example:
>cvs co Project1
>cvs update Project1
>cvs co Project2
>cvs update Project2