[
https://issues.apache.org/jira/browse/SCM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961906#comment-17961906
]
ASF GitHub Bot commented on SCM-527:
------------------------------------
jira-importer commented on issue #739:
URL: https://github.com/apache/maven-scm/issues/739#issuecomment-2964617313
**[Damian
Nowak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nowaker)**
commented
If you need to save these these temporary files, use a work-around:
```
1. while true; do chown root:root /tmp/*.commit; done
```
> Not enough information reported to enable troubleshooting
> ---------------------------------------------------------
>
> Key: SCM-527
> URL: https://issues.apache.org/jira/browse/SCM-527
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Reporter: Kohsuke Kawaguchi
> Priority: Major
>
> SVN provider for Wagon often uses a temporary file to invoke svn.exe. Such a
> file is immediately deleted, which makes it impossible for people to diagnose
> the problem when svn operation fails.
> For example, in MRELEASE-332, the user cannot replicate the problem since he
> doesn't know exactly what's in /tmp/maven-scm-248675112.commit. I just had a
> similar painful troubleshooting session.
> I suggest you leave those temporary files around if the svn execution fails,
> so that the user can just copy&paste the command line dump to the shell to
> retry the behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
