can't do an SVN commit on a repository mounted via SSHFS

[GoogleCodeExporter]

What steps will reproduce the problem?
1. checkout a SVN repository using a SSHFS mountpoint
2. change a file in what you've checked out
3. try to commit it back

What is the expected output? What do you see instead?
It sends all the data like usual in SVN, but then at the very end, it says 
"can't move xxxxxxxx/db/
transactions/27-1.txn/rev   to xxxxxxxx/db/revs/28"  which I believe is what 
happens at the 
very end of the SVN transaction. It needs to do a move, but bombs out instead.

What version of the product are you using? On what operating system?
LibFUSE 0.2.0, and the "sshfs-static" binary supplied with the 0.1.0 
application bundle on OSX 
10.4.8

Please provide any additional information below.
If you could use sshfs to do SVN checkouts/commits, this would be extremely 
useful for those of 
use who use OSX on a laptop but have code files under SVN that are sitting on 
an AFS server... 
Not sure exactly what the issue is. There seems to be some buzz about this 
issue a while ago, 
but evidently it is fixed it under Linux. I tried the "-o workaround=rename" 
but that didn't work 
for me. Perhaps I'm doing something silly?

Original issue reported on code.google.com by morganqu...@gmail.com on 14 Feb 2007 at 6:08

[GoogleCodeExporter]

I wasn't clear in step #1 what I meant:

1) Use SSHFS to mount your home directory that is sitting on a remote machine. 
Then, use SVN (with a file:/// 
path that goes through the SSHFS mount point) to check out some code off the 
remote machine and onto your 
local machine. This works great; the files come through SSHFS and onto your 
local box without issue.

Original comment by morganqu...@gmail.com on 14 Feb 2007 at 6:11

[GoogleCodeExporter]

"-oworkaround=rename" seems to work for me. Without it, I do get the "can't 
move blah" error.

Original comment by si...@gmail.com on 14 Feb 2007 at 7:47

[GoogleCodeExporter]

It has been reported to me that things work fine with workaround=rename, so 
marking this as invalid. If this fails 
for somebody with workaround=rename, feel free to open the issue.

Original comment by si...@gmail.com on 2 Mar 2007 at 6:09

• Changed state: Invalid

[GoogleCodeExporter]

Even checking out an SVN repository did not work without the workaround=rename, 
but
with it worked. Perhaps this should be mentioned more obviously somewhere, we
shouldn't have to search the issues database for a known issue like this. But I 
am
glad it was here at least. And thanks for an amazing program.

Original comment by shak...@gmail.com on 20 Mar 2007 at 7:26