Hi Alan,
On Sat, Apr 18, 2009 at 11:46 PM, Alan Wood <alan.wood_at_clear.net.nz> wrote:
> Hi Bryan,
> I'm afraid to say that this works for me. Never seen anything like this before.
>
> Before trying to investigate further are you aware of the issues with subversion
> working copies on Samba shares?
> see
> http://subversion.tigris.org/issues/show_bug.cgi?id=3053
> and a (now slightly out of date) patch for one issue here which is working for me:
>
This seems to be a different problem. Note that it used to work under SVN 1.5.
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1787
> 205
>
> Unless you have a very good reason for it, you should not use Samba for working
> copies.
>
> Having said that, I do use Tortoisesvn ( with patches applied ) .
I used both SVN and TortoiseSVN and they both show the same behaviour.
>
> What version of Samba are you using? or is this a CIFS box? There are plenty of
> non-confoming CIFS systems out there.
>
Actually I don't really have a clue. The server is a NAS, a Maxtor
Shared Storage Plus. It runs the following samba:
# /usr/local/samba/sbin/smbd --version
Version 3.0.2
What I think is the problem, is that SVN recognizes all files as
directories, and therefore tries to load the .svn directory from
dir/file.ext/.svn instead of from dir/.svn. Maybe it is some weird
kind of interactoin between Vista x64, Samba and SVN. I will see
whether I can find an 32 bits Vista installation to test this out. As
I said before, it did work on 1.5.
> Alan
>
Regards,
Bryan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1797087
Received on 2009-04-19 04:06:43 CEST