[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn:executable is ignored on checkout form Windows to Samba share

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Wed, 28 Nov 2012 18:13:44 +0100

Hello,

I have some working copies on Samba shares, Ubuntu 12.04 LTS with all
updates installed, which are accessed using TortoiseSVN 1.7.10 which
uses Subversion 1.7.7. Some of those working copies contain executable
Perl scripts with proper svn:executable defined as *, but depending on
my Samba configuration the executable bit gets set or not. It only
gets set if Smaba is configured to force specific permissions
including the executable bit. If I checkout natively using a
Subversion client on the shell the executable bits get properly
applied.

Is the svn:executable property completely ignored on operations which
are applied using Windows clients? I thought/hoped that Windows just
ignores anything regarding svn:executable if it's done to itself but
Samba could maybe recognize those permissions. This doesn't seem to be
the case.

If Windows clients ignore applying svn:executable, do you have any
ideas on how I could configure Samba to just apply it on Perl scripts?
The shares are pretty general and I don't want e.g. CSS files to have
the executable bit set. The only solution I found was a cron job
regularly finding and fixing Perl scripts as Samba doesn't seem to
provide any file type filters.

Thanks for any hints.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2012-11-28 18:14:20 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.