On 9/12/18 9:20 PM, Stefan Seelmann wrote: > On 9/12/18 9:17 PM, Stefan Seelmann wrote: >> On 9/12/18 9:09 PM, Stefan Seelmann wrote: >>> On 9/12/18 8:55 PM, Shawn McKinney wrote: >>>> Hi all, >>>> >>>> running through the checklist on fortress release, deploying to production >>>> website, changes made to staging. >>>> >>>> I’m getting this error and unsure how to proceed: >>>> >>>> production/directory/content/studio/users-guide/2.0.0.v20180908-M14' >>>> already exists >>>> >>>> does this ring a bell? >>> >>> Hm, I pushed the Studio user's guide for the current in-vote release >>> already to the production website, but also added it to >>> content/extpaths.txt in trunk (and thus staging) >>> >>> On staging it's there: >>> svn cat >>> https://svn.apache.org/repos/infra/websites/staging/directory/trunk/content/extpaths.txt >>> >>> On prod it's not yet there: >>> svn cat >>> https://svn.apache.org/repos/infra/websites/production/directory/content/extpaths.txt >>> >>> >>> But I don't know what to do... >> >> I'll delete the >> production/directory/content/studio/users-guide/2.0.0.v20180908-M14 >> folder, and the try to publish... >> > > Ah, wait. Maybe the reason is that in extpaths.txt the new docs I put > into a subfolder, but the parent is already defined in extpaths. I'll > remove the child... > > # Studio > studio/users-guide > studio/users-guide/2.0.0.v20180908-M14 >
Seems this worked, it's published :) Sorry for the trouble.
