[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS bug? Committing a new file to a branch failed and the local f il
Re: CVS bug? Committing a new file to a branch failed and the local f ile was cleared!
Tue, 30 Jul 2002 13:04:06 -0400
On Tue, Jul 30, 2002 at 11:52:44AM +0300, Reinstein, Shlomo wrote:
> cvs commit: cannot remove file2.c: Permission denied
> cvs [commit aborted]: cannot rename file CVS/,,file2.c to file2.c: File
These are the key. (Especially the first one; the second error
just confirms which copy of file2.c the first error occurred on.)
CVS was trying to replace the sandbox copy of the file with
another copy it had created, and was unable to do so.
(I don't know why it wanted to do this; since it hadn't yet
committed a revision, it seems too early to have been doing
keyword expansion. But that's immaterial; what matters is that
it tried, and failed.)
Now, as to why it failed. The error is "Permission denied". You
don't say which operating system, (or, for that matter, which CVS
version). If the sandbox lives on a UNIX machine, then the
problem would appear to be that the user has no write permission
in file2.c's parent directory. How the user created the file in
the first place, I'm not sure. Maybe the directory was chmod'ed
afterward? Maybe it's chmod'ed like /tmp on many systems --
drwxrwxrwt -- and owned by someone other than the user in
question? Dunno, but that's a simple UNIX thing.
If the sandbox is on an NT machine (or worse, if it's on a
remote-mounted file system of some sort), I can't offer any
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. address@hidden
| | /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
- Paul Schneider-Esleben