It can sort of be worked around with a "find . -name '.svn' | xargs chmod -R 755". Even after that, though, a couple users browsing their working copies kills our server--looks like ZigVersion drills down too aggressively or refreshes too frequently or something.
Our working copies are on our webserver, and they all use its local MySQL database. Working off of our own machines would be a significant hassle.
Aparajita
'm not sure what your reasoning was to share working copies like this
The reasoning is simple: I have a system that has to run under Windows, but I edit the source files on my Mac by mounting an SMB share with the source files. Since the source files live on the SMB share, I naturally want to use ZigVersion on my Mac to manage the source.
- Aparajita
eriks
I ran into the following page today, which may help out with this problem.
I'm not sure what your reasoning was to share working copies like this, but if you must do so, you may be better off going the other direction (have the working copy on the mac, and share it to the windows box).
Avi Flax
This one feature would, all by itself, get me to buy a few licenses, and to recommend the software to others as well.
The problem: I have some working copies that live on a Windows server, which I access by mounting a share via SMB/CIFS in the Finder. When I run a SVN operation on that working copy, such as update, commit, etc, I get this:svn: Can't move '.svn/tmp/entries' to '.svn/entries': Permission denied That's with any client. It seems to have something to do with the way the share is mounted.
I *may* have found a workaround involving OpenSSH, SFTP, MacFUSE, and sshfs, but it's quite convoluted, involved, and still not 100% worked out.
It'd kick ass if ZigVersion would handle this for me.
