You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Marcus (JIRA)" <ji...@apache.org> on 2016/02/11 19:40:18 UTC

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

     [ https://issues.apache.org/jira/browse/INFRA-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus resolved INFRA-11247.
----------------------------

> 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
>            Assignee: Chris Lambertus
>            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)