You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Joe Schaefer (JIRA)" <ji...@apache.org> on 2012/05/10 17:28:49 UTC

[jira] [Commented] (INFRA-4780) Failed attempt at following CMS cleanup guide

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

Joe Schaefer commented on INFRA-4780:
-------------------------------------

Your timing was bad.  When you removed the content/ directory from svn,
the first svn mv ops were still being built by buildbot.  Once that was completed
buildbot tried to check-in the changes but the svn tree was in conflict by that point.

I will clean up the mess on the cms and let you know when it's safe to run a full
site build again.
                
> Failed attempt at following CMS cleanup guide
> ---------------------------------------------
>
>                 Key: INFRA-4780
>                 URL: https://issues.apache.org/jira/browse/INFRA-4780
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CMS
>            Reporter: Ian Dickinson
>
> After a suggestion in INFRA-4754, I'm trying to follow the guidance in [1] to make our CMS site visible at jena.apache.org now that Jena has graduated.  What I did:
> * in the migrated svn tree, I svn mv'ed site/trunk/content/jena/* to
> site/trunk/content and committed
> * in https://svn.apache.org/repos/infra/websites/staging/jena/trunk/ I svn rm'ed the content/ directory
> * I made a trivial change to a template file to trigger a full site rebuild and svn committed that
> I then got a message from buildbot saying that the the rebuild failed. The critical bit from [2] is:
> """
> svn: E160013: '/repos/infra/websites/staging/jena/trunk/content' path not found
> program finished with exit code 1
> elapsedTime=104.476960
> """
> I assumed that, despite what the cleanup guide says, the build script was not expecting the content directory in staging to be missing, so I added a new content/ directory and committed that. That didn't work, I now get an svn error when I try to force a site rebuild [3]:
> """
> svn: E155015: Commit failed (details follow):
> svn: E155015: Aborting commit: '/usr/local/websites/jena/trunk/content' remains in conflict
> """
> At this point, I don't know what's going on (i.e what I've broken!) and would like some help please.
> Thanks,
> Ian
> [1] http://apache.org/dev/cmsref#cleanup
> [2] http://ci.apache.org/builders/jena-site-staging/builds/209/steps/shell/logs/stdio
> [3] http://ci.apache.org/builders/jena-site-staging/builds/212/steps/shell/logs/stdio

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira