[Top][All Lists]

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

CVS bug? Committing a new file to a branch failed and the local f ile wa

From: Reinstein, Shlomo
Subject: CVS bug? Committing a new file to a branch failed and the local f ile was cleared!
Date: Tue, 30 Jul 2002 11:52:44 +0300


A user checked-out a CVS project from a branch, modified it, added a file,
and then tried to commit. When he committed, he saw output like the
(I deliberately changed the names of the files and paths, note the problem
with file2.c below)

repository-path/Proj/file1.c,v  <--  file1.c
new revision:; previous revision: 1.5
RCS file: repository-path/Proj/Attic/file2.c,v
cvs commit: cannot remove file2.c: Permission denied
cvs [commit aborted]: cannot rename file CVS/,,file2.c to file2.c: File

C:\working-directory> cvs status Proj/file2.c
File: file2.c Status: Locally Added

   Working revision:    New file!
   Repository revision: No revision control file
   Sticky Tag:          branch_v82 - MISSING from RCS file!
   Sticky Date:         (none)
   Sticky Options:      (none)

Looking at the repository, file2.c,v exists, and it has some admin
information but no contents (trying to do "co file2.c,v" to a temporary
directory yields a 0-size file). Also, the local copy of this file (from
which it was committed) has been cleared. The local file still exists, but
has the size 0.


reply via email to

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