You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Rob Weir (JIRA)" <ji...@apache.org> on 2013/10/01 02:33:24 UTC

[jira] [Commented] (INFRA-6814) ooo-site CMS fails build: Unmergeable scheduling requested on an entry

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

Rob Weir commented on INFRA-6814:
---------------------------------

Can close this issue.  I worked around it by deleting the directory that it was complaining about and then re-adding it.  

> ooo-site CMS fails build:  Unmergeable scheduling requested on an entry
> -----------------------------------------------------------------------
>
>                 Key: INFRA-6814
>                 URL: https://issues.apache.org/jira/browse/INFRA-6814
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Rob Weir
>            Assignee: Joe Schaefer
>            Priority: Critical
>
> We've been getting a CMS build error since last night.  Most recent version is:
> http://ci.apache.org/builders/ooo-site-site-staging/builds/3708/steps/compile/logs/stdio
> Tried forcing a new wc on cms.apache.org and then updating the pull down the latest changes.  Same error came back.
> The check-in that led to the error included some directory renaming, including:
> /ooo-site/trunk/content/pt renamed to /ooo-site/trunk/content/pt.old
> /ooo-site/trunk/content/pt-test renamed to /ooo-site/trunk/content/pt
> This didn't see, to confuse Subversion when these changes were committed.  But it seems to be tripping up the CMS.



--
This message was sent by Atlassian JIRA
(v6.1#6144)