Community
Participate
Working Groups
Steps to reproduce: - Take an existing file 'file.xyz' that is checked into the CVS repository. - Copy a file with the same name from another place inside the Eclipse workspace over file.xyz. An alert appears: "'file.xyz' exists in the selected destination. Do you want to overwrite?" - Click Yes. - Now take Tortoise (or alternatively just the cvs.exe command line client) and commit file.xyz. Tortoise displays the following error: "In D:\projects\sample\src\java\de\acme\xml: C:\Programme\TortoiseCVS\cvs.exe -q commit -m file.xyz CVSROOT=:pserver:vsdd-server:/usr/local/cvs cvs commit: `file.xyz' should be removed and is still there (or is back again) cvs [commit aborted]: correct above errors first!" The cause for this behaviour is the '-' character in line "/file.xyz/-1.6/Tue Jan 16 13:37:57 2007//" from file CVS/Entries. Removing the '-' manually, fixes the problem. The context menu command "Team" - "Commit.." in Eclipse works fine anyway. I cannot tell the right way to handle this, but it should be possible to the Eclipse-CVS-UI and alternative CVS-UI's in parallel. (Also see Bug 14755 Copying over file gives CVS warning about deletion)
I suspect what is happening is this. When the copy occurs, a deletion is first performed, thus leading to the "-" in the entry line. Then when the create occurs, it is handle by CVS at a time when the entry file is not writable (i.e. certain Eclipse Resource events lock the workspace). The Eclipse CVS client ignores a deletion in the entry line if the file still exists where as other CVS clients fail. While we would like to be command line compatible, we do not have the manpower to address this particular issue at this time. Contributions are welcome.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
