Re: CVS 1.11 fails to create administrative files when using a remote repository

[Garth Winter Webb]

Why are you creating the 'alpha' directory?  A checkout should create this
directory for you.  I'm not sure why this would cause a problem for CVS,
but not knowing much about how well CVS runs under windows and that CVS
seems to be trying to find CVS/Entries indicates that its confused by the
empty directory.
        Also these examples assume a root module that you haven't
named.  For the sake of this example lets just say that the module name is
'foo'.  I would suggest this:

* Do a CVS checkout on the module you want to work on first.

$ cvs checkout foo

* To update remote hosts of file changes or added directories use 'update'
with the '-d' option

$ cd foo
$ cvs update -d

Try to be explicit as possible;  use the real module name rather
than '.'.  Use 'checkout' to create a new work area.  Use 'update' to
freshen files in an existing work area.  Use the '-d' option of update to
get any newly created directories in your work area.

Garth

On Thu, 28 Sep 2000, Trott, David wrote:

> Steps to reproduce:
> 
> On Linux (Server)
> 
> cvs co .
> mkdir alpha
> cvs add alpha
> echo hello > alpha/world
> cvs add alpha/world
> cvs commit alpha
> rm -r alpha
> mkdir alpha
> cvs co alpha
> 
> *** Works Fine ***
> 
> On Win2000 (Client)
> 
> mkdir alpha
> cvs co alpha
> 
> *** Errors ***
> 
> Additionally when I run the command:
> 
> cvs co .
> 
> On the Win2000 box with CVS version 1.11.0.1  I get the following error
> 
> cvs checkout: cannot open CVS/Entries for reading: No such file or directory
> cvs [checkout aborted]: no repository
> 
> This works fine with version 1.10.5
> 
>