[jira] [Commented] (INFRA-11247) OpenOffice CMS: No changes can be published to staging and production

["Chris Lambertus (JIRA)" <ji...@apache.org>]

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

Chris Lambertus commented on INFRA-11247:
-----------------------------------------

I see this file in staging

http://ooo-site.staging.apache.org/no-test/

says "hello"

What are you expecting to see?

I also note that an svn status in the staging dir on the cms zone is throwing some errors - this may be the root cause of the problem:

$ pwd
/usr/local/websites/ooo-site/trunk/content
$ svn status
svn: E000022: Error converting entry in directory '/usr/local/websites/ooo-site/trunk/content/de/doc/howto_2_0/draw/pics' to UTF-8
svn: E000022: Can't convert string from native encoding to 'UTF-8':
svn: E000022: in_3D_Rotationsko?\204?\136rper.png

> OpenOffice CMS: No changes can be published to staging and production
> ---------------------------------------------------------------------
>
>                 Key: INFRA-11247
>                 URL: https://issues.apache.org/jira/browse/INFRA-11247
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS
>            Reporter: Marcus
>            Priority: Blocker
>
> First of all, sorry for priority as "Blocker" but we need attention and a fix. The problem is existing since 3 weeks. Daniel Takamori (pono) has tried a few things but with no solution so far.
> I've committed a new "no-test/" dir with files inside (Norwegian translations). But it is not going to staging [1]. I can do changes in my CMS working directory or from the command line from my local PC but it's not going to the staging build - or the production build [2].
> The same when committing changes in any other already existing files and dirs.
> [1] http://ooo-site.staging.apache.org/no-test/
> [2] http://www.openoffice.org/no-test/
> Please help. Thanks a lot in advance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)