info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Incorrect CVS Entries file


From: Matt Dowding
Subject: Incorrect CVS Entries file
Date: Thu, 8 Nov 2007 11:29:39 -0000

Hi,

 

I have a problem with CVS.  I have a repository located on a Suse Linux server (CVS version XX) and am checking out code onto a Solaris 9 server (CVS version XX).  My module has the following file structure :-

 

            Module/dir1/file

            Module/dir1/subdir1/files

            Module/dir1/subdir2/files

            Module/dir1/subdir3/files

            Module/dir2/subdir4/files

 

(i.e. there is nothing in dir2 except the subdirectory, although the subdirectory itself contains several files).

 

When I perform a clean checkout of the module into a fresh working area (using cvs co Module) I get all of the files correctly.  However, if I change any of the files in Module/dir2/subdir4 a call to cvs status does not show that these files have been changed.  They also do not take on tags after check-in.

 

A quick investigation has uncovered that the CVS/Entries file under dir2 just contains D indicating no sub-directories so I assume this is where the problem lies.  What I don’t know is how to fix this.  I don’t imagine that I can change the Entries file itself since this is generated as part of the checkout, so is there a bug in CVS that I can get a fix for, or is there another file in the repository itself that I can change to fix this problem?

 

Any help much appreciated.

 

Thanks,

 

Matt

 

Matt Dowding

Monitoring & Alerting

Telesoft Technologies Ltd

This email and any attachments are confidential. It is intended for the recipient only. If you are not the intended recipient, any use, disclosure, distribution, printing or copying of this email is unauthorised. If you have received this email in error please immediately notify the sender by replying to this email and delete the email from your computer. The contents of any attachment to this e-mail may contain software viruses which could damage your own computer system. While we have taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]