On your network volume, did you try:
touch foo
mv foo bar
That would test your theory that the emptiness of the file has
something to do with it. If that gives you an error also, it's
definitely not a bug in svn. Most likely then, I'd guess, would be
the CIFS implementation on OS X.
-wsv
On May 31, 2005, at 6:28 PM, Tym Altman wrote:
> I think I figured out what's going on. The file trunk/foo/bar was
> an empty file (0 bytes). When I wrote some data into the file, and
> committed it in from my local HD, I was able to check out the full
> trunk to my SMB share.
>
> Now the question is, is it a bug in svn, SMB, Mac OS X, or some
> combination of the 3?
>
> thanks,
> tym
>
> On 31-May-05, at 5:28 PM, Tym Altman wrote:
>
>
>
>> svn (from http://homepage.mac.com/martinott/). If I check out the
>> trunk to my local directory (on my mac) it works fine. But if I
>> try to check out to a network volume, mounted using SMB, the
>> checkout fails after a few files:
>>
>> svn co http://192.168.110.175/repos1/trunk
>> A trunk/arraylengthtest.rb
>> A trunk/foo
>> A trunk/foo/bar
>> svn: In directory 'trunk/foo'
>> svn: Can't copy 'trunk/foo/.svn/tmp/text-base/bar.svn-base' to
>> 'trunk/foo/bar.tmp': Invalid argument
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
- application/pkcs7-signature attachment: smime.p7s
Received on Thu Jun 2 01:15:30 2005