Okay, so should have tried playing around just a little bit longer before posting (its always the way). Turns out the different permissions were just happanstance. The particular file name was quite long which didn't matter under OSX, but under linux my home directory is encripted which makes file names longer, pushing it over the 255 character mark.
Sorry for the spam. Robin. On 11 July 2012 18:49, Robin Shannon <[email protected]> wrote: > So I cloned a copy of a repo from my server onto my ubuntu laptop and > then when I went to open it I got an error saying that it was "unable > to open file foo.pdf for writing". So I went away and tried the same > thing on my OSX desktop and it worked fine. I then searched the error > message in the archives and found out it seemed to have to do with > permissions, and lo and behold, when I checked on the server the > permissions for foo.pdf were rwxrwxr-x where as for all the other > files they were rwxr-xr-x. I wasn't quite sure why this would matter, > but I changed foo.pdf to have the same permissions as everything else > (I also changed its name slightly so fossil would allow me to make a > commit). I then pulled this new version onto my laptop and tried > again, but that didn't seem to help, I still got the exact same error > for the same file. > > Any ideas? And any thoughts on why it should matter whether I'm > opening the repo on ubuntu rather than OSX? Or why group write > permissions should matter? > > Cheers, > Robin. > > -- > http://robinshannon.net -- http://robinshannon.net _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
