Aptana 1.5 "svn: Permission Error"

Question

I installed Aptana 1.5 today, but after installation all my SVN projects give me this error when I try to commit, update, restore, etc .:

Access is denied. svn: Error resolving case of 'C:\Users\Brayn\My Documents\Aptana Studio Workspace\PentruConstrucii' 

I uninstalled my previous version of aptana, reinstalled aptana 1.5, changed my workspace and still gives me this error.

Do you know what it could be?

Answer 1

" C:\Users " means Windows Vista or 7 ...
This may be due to the way SVN handles the Windows Vista symbolic link (“ connection ”): bad, according to this ticket (also described in error 3208 ):

This error is reproduced in 100% of cases.

1) If you call " svn delete " on a Windows Vista symbolic link, for example, " c:\documents and settings\<username>\my documents\<some path> ", then Subversion will fail "svn: Solution failed" C:\Documents and Settings\<username>\my documents\<some path> "'"

2) If you set the current working directory to " C:\Documents and Settings\<username>\my documents\<some path> " and cause " svn delete " against the local file name, the operation is performed flawlessly.

This may be due to some ACL rights that prevent SVN data access:

Subversion tries (via APR) to resolve the exact case of all the paths passed to it. This fails because this particular example has a path that is unreadable in its path.
You can see it through:

 C:\>cacls "c:\Documents and Settings" C:\Documents and Settings Everyone:(DENY)(special access:) FILE_READ_DATA 

I know that you are referencing C:\Users here, but maybe SVN try the internally old path.

Answer 2

I had the same error display if I end the directory name with \ from the cmd.exe shell:

 C:\> svn co http://my/repo/ "C:\Work\My Repo\" svn: Error resolving case of 'C:\Work\My Repo"' C:\> svn co http://my/repo/ "C:\Work\My Repo" UC:\Work\My Repo Checked out revision 13768. 

I think this ends up interpreting the final \" as an escaped double quote, rather than a backslash and end of line.

Answer 3

Old question, but I had a related and similar problem with a solution that is relevant to this:

My (unrelated electronic design automation) triggered svn: Error resolving case of "<blah blah> errors, followed by what looked like my commit log message. In the end, I realized that some double quotes ( " ) that I used for log messages were interpreted as the completion of the message, then the rest of my babble was taken as an entrance to svn. My solution was just to use single quotes.

In your case, it sounds like your program (Aptana) might be scared, because when it sees spaces in the path name, it covers the path in quotation marks, maybe something will break (redundant quotes?). This will be allowed if you just work in the root directory of C:\ , because in the root path of the WC ...\My Documents\... there are no spaces.