Did a bit on googling on this issue. There are now at least four
threads already here in this newsgroups, starting in December 2005 with
the following subject lines:
12/ 2005: Another SVN Permissions Problem (
03/ 2006: Issue on a mounted volume on osx
11/ 2006: commit, with working copy on SMB share not working
06/ 2007: Commit failed: 'Can't copy ... Input/output error'
Other reports on the net:
http://sonicchicken.net/blog/wordpress/2006/03/11/progress-on-scplugin/#comment-701
(see comment #3)
http://www.chriscassell.net/log/2007/01/09/subversion_quir.html
Somebody seems have tracked down a bug in Samba that caused problems
with subversion and is working on a patch. He does not specify the
precise problems in subversion and is using VMS not Mac OS X but the
error messages are the same:
http://lists.samba.org/archive/samba-vms/2006-May/001649.html
The common thread is always a working copy on a Samba share and
subversion running on Mac OS X 10.4.x and the failure to commit a file.
Some of the comments report a 'permission denied' but most report an
'Input/output error' trying to copy to
'text-base/filename.txt.svn-base.tmp' (where filename.txt' is the file
on which subversion chokes).
Subversion' versions vary from 1.2.x to 1.4.x. Samba share can be
hosted on Windows or Linux. Most importantly several people report this
problem only for empty files and verified it (11/ 2006 and
chriscassel). My experience supports this finding. I can add that if an
empty file has been added from a non-SMB working copy, checking out or
updating a working copy to an SMB share also fails, even if the empty
file has been exchanged with a non-empty file. It apparently is
sufficient that somewhere in the history of the repository an empty
file was present.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 8 17:11:24 2007