[
https://issues.apache.org/jira/browse/SCM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962174#comment-17962174
]
ASF GitHub Bot commented on SCM-594:
------------------------------------
jira-importer commented on issue #804:
URL: https://github.com/apache/maven-scm/issues/804#issuecomment-2964625021
**[Steffi
Tinder](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stinder)**
commented
To make it easier for people to find this bug (and the workaround!):
One possible symptom is the following error message when preparing a release:
"Kann \<svn-url> in Revision 0 nicht im Projektarchiv finden" (German for
"Unable to find repository location for \<svn-url> in revision 0")
The workaround is to unset LC_ALL before executing mvn release:prepare (or
any other maven command that parses svn output).
> maven-scm-provider-svntest fails with a localized $LC_ALL
> ---------------------------------------------------------
>
> Key: SCM-594
> URL: https://issues.apache.org/jira/browse/SCM-594
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.4
> Environment: Linux
> Reporter: Torsten Werner
> Priority: Major
>
> maven-scm-provider-svntest sets LC_MESSAGES=C but that does not help if
> LC_ALL has been set to some incompatible value by the user. It should either
> set LC_ALL=C or unset LC_ALL in combination with LC_MESSAGES=C.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
