[
https://issues.apache.org/jira/browse/SVN-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177863#comment-17177863
]
Nathan Hartman commented on SVN-4622:
-------------------------------------
I reproduced it with 1.10. It's easy to reproduce and doesn't require involving
root. Just change the ownership of a file:
{code:java}
$ svn co -q https://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts
$ cd hook-scripts
$ sudo chown nobody svnperms.conf.example
$ ls -l svnperms.conf.example
-rw-rw-r-- 1 nobody nate 3147 Aug 13 23:32 svnperms.conf.example
$ svn revert -R .
Reverted 'svnperms.conf.example'{code}
The above revert has no effect on the file's contents, ownership, or
permissions.
Speaking of permissions, change the file's permissions to 664 and we no longer
see output from 'svn revert':
{code:java}
$ sudo chmod 664 svnperms.conf.example
$ ls -l svnperms.conf.example
-rw-rw-r-- 1 nobody nate 3147 Aug 13 23:32 svnperms.conf.example
$ svn revert -R .
{code}
No output with the above.
But change it back to 644, and we get the output again:
{code:java}
$ sudo chmod 644 svnperms.conf.example
$ ls -l svnperms.conf.example
-rw-r--r-- 1 nobody nate 3147 Aug 13 23:32 svnperms.conf.example
$ svn revert -R .
Reverted 'svnperms.conf.example'
{code}
It was reported to be seen with 1.13 on
[IRC|https://colabti.org/irclogger/irclogger_log/svn-dev?date=2020-08-12].
See mail thread ["Svn revert and file permissions
bug"|https://lists.apache.org/thread.html/rdc7ebee17db12855f5749333b5a45b8fe89b608099920a7d40cf09bb%40%3Cusers.subversion.apache.org%3E]
on 2020/08/13.
> revert as root always notifies for files
> ----------------------------------------
>
> Key: SVN-4622
> URL: https://issues.apache.org/jira/browse/SVN-4622
> Project: Subversion
> Issue Type: Bug
> Components: libsvn_subr
> Affects Versions: all
> Reporter: Philip Martin
> Priority: Minor
>
> $ svnadmin create repo
> $ svn import -mm repo/format file://`pwd`/repo/f
> $ umask 0022
> $ svn co file://`pwd`/repo wc
> $ sudo svn revert wc/f
> Reverted 'wc/f'
> The function svn_io__is_finfo_read_only() will check the world permissions
> when invoked with uid=root. A typical umask removes world write so this means
> that root sees every file as read-only. This causes the revert code to invoke
> svn_io_set_file_read_write() and notify. However svn_io_set_file_read_write()
> sets the owner permissions, an operation that succeeds when run as root, and
> obeys the umask so the world permissions remain read-only.
> Reported by:
> https://mail-archives.apache.org/mod_mbox/subversion-users/201602.mbox/%3C56C0738E.9010508%40i.ua%3E
> http://svn.haxx.se/users/archive-2016-02/0061.shtml
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
