Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.4.x
Description
The following goes only for files, there should be another issue for directories. The 'missing' status (!) does not differentiate between files that are already in repository and files that were only scheduled for addition. This leads to unexpected behaviour when user tries to update or revert missing scheduled for addition file (while user thinks this file is in repositiory and only missed in her working copy, based on its status): * svn revert - just removes file metadata, no file restored * svn update - currently leads to error: svn: Can't copy '.svn\text-base\foo.svn-base' to '.svn\tmp\foo.tmp.tmp': The system cannot find the file specified. Here is the thread in subversion-users list: "Failed to update missing (!) added (A) files" http://subversion.tigris.org/servlets/BrowseList? list=users&by=thread&from=571257
Original issue reported by fuurin