You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Johan Corveleyn (JIRA)" <ji...@apache.org> on 2018/12/14 09:30:00 UTC
[jira] [Commented] (SVN-4797) Executable file modes are reset when
updating a file with no svn:executable property
[ https://issues.apache.org/jira/browse/SVN-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721097#comment-16721097 ]
Johan Corveleyn commented on SVN-4797:
--------------------------------------
For completeness: if I'm not mistaken, this issue was discussed on IRC #svn with [~julianfoad]:
https://colabti.org/irclogger/irclogger_log/svn?date=2018-12-13#l94
> Executable file modes are reset when updating a file with no svn:executable property
> ------------------------------------------------------------------------------------
>
> Key: SVN-4797
> URL: https://issues.apache.org/jira/browse/SVN-4797
> Project: Subversion
> Issue Type: Bug
> Components: cmdline client
> Affects Versions: 1.9.9
> Reporter: Sinus Pi
> Priority: Minor
>
> The command-line client resets +x flags on files it updates, if they lack an svn:executable flag.
> As demonstrated here:
> {noformat}
> $ echo Test file >foo
> $ svn add foo
> A foo
> $ svn commit foo -m test
> Adding foo
> Transmitting file data .done
> Committing transaction...
> Committed revision 101.
> $ ls -al foo
> -rw-rw-r-- 1 usr grp 10 Dec 13 17:24 foo
> $ chmod a+x foo
> $ ls -al foo
> -rwxrwxr-x 1 usr grp 10 Dec 13 17:24 foo
> ^--^--^--- file is executable as much as it can get.
> ... the file was edited and committed in a second working copy ...
> $ svn up foo
> Updating 'foo':
> U foo
> Updated to revision 102.
> $ ls -al foo
> -rw-rw-r-- 1 usr grp 17 Dec 13 17:26 foo
> ^--^--^--- file is executable no more.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)