[
https://issues.apache.org/jira/browse/SVN-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802048#comment-17802048
]
Daniel Sahlberg commented on SVN-4440:
--------------------------------------
Regarding on Brian's comment:
The changing of the executable flag is by design. If a file should be
executable, it should have the property svn:executable set:
{{# svn propset svn:executable '*' test.py}}
{{property 'svn:executable' set on 'test.py'}}
This issue should stay resolved.
> Subversion sets permissions on files, when it shouldn't
> -------------------------------------------------------
>
> Key: SVN-4440
> URL: https://issues.apache.org/jira/browse/SVN-4440
> Project: Subversion
> Issue Type: Bug
> Components: libsvn_subr
> Affects Versions: 1.8.x
> Reporter: Subversion Importer
> Priority: Critical
> Fix For: ---
>
>
> {noformat:nopanel=true}
> As discussed in this thread:
> http://svn.haxx.se/users/archive-2013-10/0095.shtml, subversion sets file
> permissions on files at commit.
> The file doesn't have svn:eol-style, svn:keywords or svn:needs-lock properties
> set, and subversion doesn't rewrite it (it has the same inode before and after
> the commit).
> So according to these and judging from this mail:
> http://svn.haxx.se/users/archive-2013-10/0180.shtml, I consider this a bug,
> which not only prevents one from maintaining file permissions and ownership in
> subversion properties (subversion will set the file to umask permissions on
> every commit), but this behaviour is not expected from the user, and can pose
> ill effects.
> Please remove this by deleting the chmod from the commit codepath (from a
> simple
> grep, it seems to be called from subversion/libsvn_subr/io.c, so I choose that
> subcomponent).
> I set "found in version" to 1.8.x, but I'm sure it's in 1.7, and not sure
> about
> earlier versions.
> Thanks.
> {noformat}
> Original issue reported by *bra*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
