>Submitter-Id:   net
>Originator:     Mike Charnoky
>Organization:   Nextbus
>Confidential:  no
>Synopsis:      cvs export failure with remote repository
>Severity:      non-critical
>Priority:      low
>Category:      cvs
>Class:         sw-bug
>Release:       cvs-1.10.8
>Environment:
System: Linux beret.corp.nextbus.com 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 i586 
unknown
Architecture: i586
>Description:
When "cvs export" is used to export the same file, two or more times in a
row, using a remote repository only (not a local repository), the command
fails with the error:

cvs export: cannot open CVS/Entries for reading: No such file or directory
cvs [export aborted]: no repository

This is not a serious problem, but it makes me wonder if something more
serious might be broken.  Since this is an export command, the
local CVS/Entries (or _any_ local CVS files) should not be accessed at all.
Why is the Entries file being accessed?  Why only when using a remote
repository?  The problem does not occur when the reposittory is local.
>How-To-Repeat:
1) Export a file from cvs, SPECIFICALLY specifying a remote
   user and repository.  NOTE: I am using ssh v1.2.26 for CVS_RSH

> cvs -d cvsuser@cvshost:/my_cvs_home export -D now my_cvs_module
U my_cvs_module

   This works fine.  The file is sucessfully exported from CVS.

2) Now try the same command again:

> cvs -d cvsuser@cvshost:/my_cvs_home export -D now my_cvs_module
cvs export: cannot open CVS/Entries for reading: No such file or directory
cvs [export aborted]: no repository

   This time the command fails.  For some reason, cvs is attempting
   to access CVS/Entries, but this should not be happening for an export.

NOTES:
1) This failure only occurs when "user@repository" is specified,
   even if the repository is on the local machine.  This failure
   does not occur if the repository is specified as simply a path
   on the local machine.
2) This is happening with cvs clients 1.10.6 & 1.10.8 for Linux.
   Also 1.10.5 for FreeBSD.  I haven't tested any other
   versions/platforms.
3) I haven't tested with rsh as opposed to ssh.
4) Here is a trace with more useful info:

> cvs -t -d cvsuser@cvshost:/my_cvs_home export -D now my_cvs_module
cvs export: notice: main loop with CVSROOT=cvsuser@cvshost:/my_cvs_home
 -> Starting server: ssh cvshost -l cvsuser cvs server
S-> do_module (my_cvs_module, Updating, , )
cvs export: cannot open CVS/Entries for reading: No such file or directory
cvs [export aborted]: no repository
>Fix:
well, don't export the same file twice.  aside from that, I don't know

        

Reply via email to