www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Pescetti (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-10064) CMS error: Can't convert string from 'UTF-8' to native encoding
Date Sat, 15 Aug 2015 21:17:46 GMT

    [ https://issues.apache.org/jira/browse/INFRA-10064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698457#comment-14698457

Andrea Pescetti commented on INFRA-10064:

A quick investigation seems to yield that the CMS dies in the block in lines 33-38 of 
and (based on the error message and search engines results) this appears to be frequently
related to svn not seeing an UTF-8 locale in its execution environment and it is fixed by
$ export LC_CTYPE=en_US.UTF-8
before its execution. A quick search for "Can't convert string from 'UTF-8' to native encoding"
will give you more details, including why svn does not see the externally defined locale in
some cases.

Now, I haven't investigated how to prepare the SVN environment in the actual Perl code in
SVNUtil.pm, but at least this gives an idea of what is going on there.

> CMS error: Can't convert string from 'UTF-8' to native encoding
> ---------------------------------------------------------------
>                 Key: INFRA-10064
>                 URL: https://issues.apache.org/jira/browse/INFRA-10064
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS
>            Reporter: Andrea Pescetti
> The latest OpenOffice site builds
> https://ci.apache.org/builders/ooo-site-site-staging/
> failed apparently due to the handling of filenames containing special (non-ASCII) characters.
> Sample log:
> https://ci.apache.org/builders/ooo-site-site-staging/builds/10/steps/compile/logs/stdio
> Note: this blocks all OpenOffice site updates.

This message was sent by Atlassian JIRA

View raw message