Claudius Regn wrote:
>For Windows XP, the working copy is at H:\testsymlinks. There is a
>folder in the hierarchy parallel to testsymlinks called externaldir,
>i.e. the target of externallink exists (for Linux' eyes).
>
>Executing SVN Update #1:
>
>Popup saying "Failed to add file 'H:/testsymlinks/externallink': object
>of the same name already exists"
> then: the regular "SVN Update... Finished!" dialog shows up without
>any contents (files).
>
>Executing SVN Update #2:
>
>No Popup. Only dialog "SVN Update... Finished!" showing:
> Updated H:\testsymlinks
> Completed At Revision: 1
>
>Executing SVN Update #3: see #1 and so on.
>
>
Do you get these same problems when using the command-line client? If
not, it is only a TSVN problem.
However, the fact that your WC is on H: leads me to believe you are
directly accessing a Linux directory that is mounted over a Samba share.
If that's what you are doing, I highly suspect your problems arise from
that. Samba would make the linked directory appear to be a real
directory, and SVN/TSVN wouldn't know the difference. So when it tries
to update the svn:special file which is really a symbolic link, Samba
doesn't let it because it thinks it's a directory.
So the solution would be to either prevent Samba from resolving symbolic
links, or (better yet) don't access a Linux WC via Samba.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 13 17:41:10 2005