On 7/3/06, urs hardegger <uhardegger@gmx.ch> wrote:
[snip]
> I encounter the same problem using working-copies on samba-drives.
> The reason this happens is due to problems when the svn-client tries
> to change the file permissions in the wc. As unix filesystems do
> allow permission changes on files only if the acting user is owner,
> windows uses special flags to promote this permission to non-owners.
>
> Usually the samba setup ensures read/write access to the connecting windows
> user (usually by group permissions). In my opinion the svn-client should
> try to perform the file-permission operations more carefully (i.e. the client
> should not fail and report an error upon "unnecessary permission changes"
> if the following operation works well !!)
>
> urs.
I don't think I was being clear -- Subversion never changes any
permissions on Windows. It can't because the permission-changing
functions are not even implemented in APR on Windows.
The only thing Subversion changes on Windows is the read-only
attribute which is not a permission at all -- it is a file attribute
and is just a hint to the user. If Samba has some difficulty
supporting this file attribute (maybe because of how they map it to
unix permissions or something) then that is a problem in Samba.
Can you recreate this problem on a local disk or on a native Windows
network share (not Samba)? Perhaps it is a different problem than it
seems to be.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 3 16:18:52 2006