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

Branko Čibej (JIRA) <[email protected]>
Newsgroups gmane.comp.version-control.subversion.issues
Message-ID <[email protected]>
     [ https://issues.apache.org/jira/browse/SVN-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Branko Čibej resolved SVN-4806.
-------------------------------
    Resolution: Fixed

Fixed on trunk in r1854072 and r1854074.

> 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
>            Assignee: Branko Čibej
>            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)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.