subversion-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SVN-4440) Subversion sets permissions on files, when it shouldn't
Date Thu, 14 Jun 2018 10:26:00 GMT

    [ https://issues.apache.org/jira/browse/SVN-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512278#comment-16512278
] 

Brian  commented on SVN-4440:
-----------------------------

Looks like this bug still exists, at least with subversion clients provided by Ubuntu 16.04
(same problem on Ubuntu 14.04 too). Can this be fixed?
{code:java}
root@testbox:/home/test# svn --version
svn, version 1.9.3 (r1718519)
compiled Aug 10 2017, 16:59:15 on x86_64-pc-linux-gnu
<snip>
root@testbox:/home/test# ls -la test.py
-rwxr-x--- 1 root mygroup 10991 Jun 14 10:16 test.py
root@testbox:/home/test# emacs test.py
root@testbox:/home/test# ls -la test.py
-rwxr-x--- 1 root mygroup 11004 Jun 14 10:18 test.py
root@testbox:/home/test# svn ci test.py -m "test"
Authentication realm: <https://svn.domain.com:443> Subversion repository
Password for 'root': ********

Sending test.py
Transmitting file data .done
Committing transaction...
Committed revision 58761.
root@testbox:/home/test# ls -la test.py
-rw-r----- 1 root mygroup 11004 Jun 14 10:18 test.py

{code}
 

> 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
(v7.6.3#76005)

Mime
View raw message