[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Very odd cvs rm behavior, file not sent to the Attic
From: |
Sarah Gonzales |
Subject: |
Very odd cvs rm behavior, file not sent to the Attic |
Date: |
Fri, 19 Aug 2005 16:34:47 -0500 |
Hello to all!
I'm experiencing some *very* odd behavior when a user attempted to
remove a file from a repository and would appreciate some help. User
removed a file correctly using cvs rm filename, but when he committed
the file, he received a permissions error.
cvs commit: cannot rename PathToFile/util.h,v to
PathToFile/Attic/util.h,v: Permission denied
The permissions on the Attic are correct and this user is in the *NIX
group and the group has write perms.
drwxrwxr-x 272 28 Apr 2004 Attic
The odd behavior is this...
1. the file doesn't appear in the Attic (as you would expect if the
permission to remove was denied)
2. the file util.h,v still exists in the src/ directory where it
lived originally
3. if we run a cvs co on the repository, util.h is NOT checked out
(desired since he attempted to remove it), but it does NOT live in
the Attic, it's still in its original directory.
If I run cvs log, it indicates it was deleted and is in a "dead
state", but again, it's not in the Attic, it's in its original directory
RCS file: PathToFile/src/util.h,v
Working file: util.h
head: 1.2
branch:
locks: strict
access list:
symbolic names:
R_1_1_6: 1.1
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
----------------------------
revision 1.2
date: 2005/08/18 19:25:59; author: username; state: dead;
lines: +0 -0
Removed obsolete files
----------------------------
I also ran the validation script and it doesn't appear that our
repository is corrupted
perl validate_repo.pl
Total Files: 210 Corrupted files: 0 Invalid revs: 0 Extra files:
1 Ignored Files: 0
Total Revisions: 574 Interesting Revisions: 380
Any help is appreciated
thx,
- Very odd cvs rm behavior, file not sent to the Attic,
Sarah Gonzales <=