[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN Copy to NTFS junction denied

From: Stefan Hett <stefan_at_egosoft.com>
Date: Fri, 12 Aug 2016 16:32:52 +0200

On 8/12/2016 3:21 PM, Bruno Gustavs wrote:
> TortoiseSVN on Windows 10 64bit, German language pack.
> Working directory D:\Work
> Subdirectory D:\Work\sub
> File D:\Work\sub\somefile
> Move D:\Work\sub to C:\OneDrive\sub
> mklink /J "D:\Work\sub" "C:\OneDrive\sub"
> everything works fine (add, commit).
> Problem:
> Right drag D:\Work\sub\somefile to the same directory D:\Work\sub
> In context menu choose other..., SVN Copy and rename versioned item here
> Choose new name "otherfile"
> Error messge: Subversion reported an error: "D:\Work\sub" is not a
> directory
> I assume that TortoiseSVN checks if the destination is a directory
> before starting the copy operation and does not recognise the junction
> as a valid directory.
> Workaround: Copy file directly and the new file to Subversion.
> Drawback: File history is cut.
> Other ideas?
> Related issues: #539 Junctions marked as versioned (fixed)
> Related discussions:
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=402808
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=645452
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=309433
> Best Regards
> Bruno
SVN doesn't fully support Windows junction points yet (see [1]). You can
give it a try to see whether "svn cp [source] [dest]" works. If it
doesn't I'd assume the issue with the other case is related to the SVN
limitation as well.
Workaround: Use a checkout not relying on junction points and perform
the copy operation there.

[1] https://issues.apache.org/jira/browse/SVN-3570

Stefan Hett
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-08-12 16:33:09 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.