You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Kub <st...@gmail.com> on 2009/07/03 09:46:44 UTC

Re: Subversion bug when performing actions on individual files on a Samba share

Hi,
I've got the same problem on a samba share, winxp and tortoisesvn.

It seems that it appear on tsvn 1.5.8.



-- 
View this message in context: http://www.nabble.com/Subversion-bug-when-performing-actions-on-individual-files-on-a-Samba--share-tp23112394p24320393.html
Sent from the Subversion Dev mailing list archive at Nabble.com.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2367757

Re: Subversion bug when performing actions on individual files on a Samba share

Posted by Alan Wood <Al...@clear.net.nz>.
On 3 Jul 2009 at 2:46, Kub wrote:

> Hi,
> I've got the same problem on a samba share, winxp and tortoisesvn.
> 
> It seems that it appear on tsvn 1.5.8.
> 
A bit more context would be nice, so here it is from the beginning of the  thread in 
April.

Z: is a maxstor NAS with Samba 3.0.2
Z:\>svn checkout http://svn.collab.net/repos/svn/trunk/www/
[...]
Checked out revision 37352. 

Z:\>svn rm www\index.html
svn: Can't open file 'www\index.html\.svn\entries': De mapnaam is ongeldig. 

The error printed here is the windows error 267 "ERROR_DIRECTORY" which 
from the windows help is described in full as "The directory name is invalid". 
Doesn't help much. On Vista it has been associated with permission issues so 
checking permissions would be a good idea.

This error code could be from the Samba server or client but from looking in the apr 
code is not translated into APR_ENOENT or APR_ENOTDIR which are the codes 
which are checked for to determine if the path is a working copy 
directory.

If you can patch the subversion source (apr actually) then adding 
ERROR_DIRECTORY to APR_STATUS_IS_ENOENT in apr_errno.h should fix 
it.

A totally different tack if you don't mind the risk is to use a 
trunk version of subvesion as the .svn folder is not used for the 
purpose of checking if a file is under revision control. Be warned 
that the working copy format has changed so you can't use a working 
copy created by trunk with 1.6 or earlier clients and as it is 
trunk, stability is not guaranteed. This new layout will be released 
with version 1.7 of subversion.

As I believe that the issue is not in the trunk version of svn and 
the best fix is actually in the apr library your chance of getting 
anything changed is minimal. If however you still have a problem 
using the trunk version I would be interested in looking further 
into the issue.

Good luck
Alan Wood

 
> 
> -- 
> View this message in context: http://www.nabble.com/Subversion-bug-when-performing-actions-on-individual-files-on-a-Samba--share-tp23112394p24320393.html
> Sent from the Subversion Dev mailing list archive at Nabble.com.
> 
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2367757

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2367931