ZigZig Forums  


Post a new message in "Problems/Bugs"
Name:
email*:
Subject:
This image contains a scrambled text, it is using a combination of colors, font size, background, angle in order to disallow computer to automate reading. You will have to reproduce it to post a message in the forums. Enter the text in the image:
topic icon:
no
boardcode:
 Colour:  Size:   Close all tags
Message:

emoticons
B) ;) :) :P
:laugh: :ohmy: :sick: :angry:
:blink: :( :unsure: :kiss:
:woohoo: :lol: :silly: :pinch:
:side: :whistle: :evil: :S
:blush: :cheer: :huh: :dry:
* - your email address will never be displayed on the site.

Topic History of: not-valid working copy error
Max. showing the last posts - (Last post first)
Author Message
Jamie Hoover I have the exact same problem. I use macfuse to mount my ubuntu vmware local development environment via sshfs. I updated to the the latest macfuse, hoping that was the problem, but the bug remains. I would really love to keep using ZigVersion. Any thoughts on a solution?
Glenn I have a remote fileshare mounted onto my Desktop using MacFUSE (SSH). I checked out an svn project into the remote fileshare which has 777 permissions. Seemed to work fine. However, when I relaunch ZigVersion it checks the same fileshare and says "...no longer appears to be a valid working copy. Would you like to remove it from the list of working copies?"



I can re-check out the same project to the same existing working copy and it fixes the error, but it never sticks. I have to do this every time I launch ZigVersion. Is this a MacFUSE problem, SVN problem, or ZigVersion bug? I know this is an odd scenario because I'm not using a local working copy but it is too cumbersome to check out a local un-testable copy and dupe every change I make into the remote server to test.