[jira] [Commented] (SVN-4806) svn cleanup fails on read-only files (windows)

["Branko Čibej (JIRA)" <ji...@apache.org>]

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

Branko Čibej commented on SVN-4806:
-----------------------------------

This is probably caused by a bug in {{svn_io_dir_remove_nonrecursive()}} in {{subversion/libsvn_subr/io.c}}. Unlike {{svn_io_remove_file2()}} in the same file, this function does _not_ clear the read-only flag on the directory on Windows.

> svn cleanup fails on read-only files (windows)
> ----------------------------------------------
>
>                 Key: SVN-4806
>                 URL: https://issues.apache.org/jira/browse/SVN-4806
>             Project: Subversion
>          Issue Type: Bug
>          Components: cmdline client
>    Affects Versions: 1.10.2
>         Environment: Windows 7, using the 1.10.3 command line tools (from TortoiseSVN).
>            Reporter: Mark Cooke
>            Priority: Minor
>
> Discussed on mailing list: [https://svn.haxx.se/users/archive-2019-02/0024.shtml]
> Our build script copies files and folders into the source tree before building the application and installer applications.  The copied-in files and folders are set as read-only by another script and {{svn:ignored}}:
> {noformat}
> root
>  > folder 1 (svn:ignore *)
>     > folder 2
>        > folder 3
> {noformat}
> When I run {{svn cleanup}} using both {{remove}} flags, svn fails with the error:
> {noformat}
> svn: E720005: Can't remove directory 'root\folder1\folder2\folder3': Access is denied.
> {noformat}
> My workaround is to add to my script to clear the read-only flag before running {{svn cleanup}}.
> As Brane replied:
> bq.  Yes, it's worth fixing, because it's a bug. :) If we have the --remove-unversioned option and it happens not to work because we fail to clear the read-only bit on files within unversioned directories, well, we should fix that.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)