Would each committer who has ever committed our site changes, please tidy up their local "site-author" directory.
The only PDF docs that should be in the "build/forrest-docs/" directory are the following: ./build/forrest-docs/dtdx/document-v13.pdf ./build/forrest-docs/dtdx/document-v20.pdf All other previously generated PDFs need to be removed so that they do not get re-deployed. Another way might be to remove the complete contents of "build/forrest-docs/" and so let it all be re-generated. -David David Crossley wrote: > Gav... wrote: > > Obviously something is not right with my setup. This was an otherwise clean > > and up to date checkout, only changing the live-sites file. > > This is on my linux Ubuntu machine. > > > > I'll look into it. > > When the production of PDF docs was disabled (see dev list). > Each of us who has/is committing the site changes > needs to clean out our local site "deploy" directory. > I mean remove the PDFs that are lingering from an old run, > so as not to re-deploy them. IIRC then this is the same > problem with any "deleted" documents. > > IIRC, i used "diff -rq" and some grep to get a list > of differences between the "generated" set of docs > and the "deploy" set of docs (sorry cannot remember > the directory names under site-author), then turned > that list into a shell-script of 'svn rm' commands. > > See FOR-1200 around 21 June 2010. > > -David > > > > Author: gmcdonald > > > Date: Tue Jul 27 05:45:13 2010 > > > New Revision: 979542 > > > > > > URL: http://svn.apache.org/viewvc?rev=979542&view=rev > > > Log: > > > Publish from forrestbot > > > > > > Added: > > > forrest/site/asf-infrastructure.pdf (with props) > > > forrest/site/committed.pdf (with props) > > > forrest/site/compliance.pdf (with props) > > > forrest/site/contrib.pdf (with props) > ... >
