On Sep 2, 2009, at 16:12, Jack Repenning wrote:
> Over in http://scplugin.tigris.org, we have a user on a Mac trying
> to do Subversion in working copies that are mounted from a Windows
> file server. See this thread:
>
> http://bit.ly/2zuVrN
>
> ... but skip the first few posts, about having the wrong SVN
> version. We fixed that. Also, ignore the temporary confusion over
> whether working copies are being shared; we confirmed they're not.
>
> What that leaves us with is: Mac SVN clients in working copies
> mounted from a Windows file server, resulting in "failure to rename"
> stuff from various .svn/tmp/ places to corresponding non-tmp places.
>
> We found this discussion here, in this list:
>
> http://bit.ly/id7zi
>
> that reports the same symptom, and fixes it with a file-server
> reconfiguration. But in this case, the file server is actually UNIX-
> hosted SAMBA, not true Windows: the configuration details are
> certainly utterly different, and there's no compelling reason to
> suppose the same settings even exist, let alone that they're made in
> the same way.
>
> So: anyone have this working? Any hints how?
I worked in a web design shop where we had a similar setup -- each
developer had his own working copies in his ~/public_html on our Linux
development server, and accessed them via SMB from Windows.
TortoiseSVN had no trouble checking out or dealing with existing
working copies. I was the only Mac guy, and my svn did not like those
working copies at all. I forget what errors I got, and it was many
versions of Subversion ago, but I resigned myself to logging in to the
Linux server with ssh and doing all svn operations that way on the
command line. I went on the assumption that what I was trying to do
was unsupported so I found a workaround.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390487
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-03 03:05:51 CEST