May 8, 2012 at 4:03 AM
Edited May 17, 2012 at 12:23 AM
While I realize this thread is a bit old, I do have some insight for those who might be following it through subscriptions or might stumble across it.
This error occurs when a file path being migrated to SVN from VSS includes an intermediate folder between the project root and the file itself that has been created on the client, but not updated to SVN. When an attempt is made to call the Status() method
against the file, SVN interprets the request as arising from a folder that doesn't exist in the project, and is not an independent project, and with no local .svn folder on the client, returns the "xxx is not a working copy" error.
For example, from the VSS side:
causes VSSMigrate to create
When VSSMigrate calls the Status() method for this local file, its premature because the "Folder" component exists only on the local client (checkout folder). As a result, because Folder is neither an independent project with its own hidden .svn file structure,
nor has it been properly COMMITed back to SVN, Subversion throws the "File.txt is not a working copy" error. The solution is to ensure all intermediate paths between the project root and the file name have been updated back to SVN before calling Status.. I'm
working on this problem myself, and expect that the solution would be to call Update against the project root before Status() is called.
My only concern is that the real issue should be that the "Folder" folder should be called as a separate creation (as a folder) back to SVN before any files are migrated, and the real fix might be to ensure the file/folder lists are being created properly.
EDIT: Corrected some errant terminology