On 11/30/05, David Crossley <[EMAIL PROTECTED]> wrote: > Tim Williams wrote: > > David Crossley wrote: > > > Tim Williams wrote: > > > > I've still never been able to update our public site with Forrestbot. > > > > I periodically retry, thinking I'm doing something wrong but no luck. > > > > It consistently fails in the deploy phase of the instructions in /etc. > > > > I've pasted the output below. We've gone through this before > > > > unsuccessfully but I'd really like to be able to get this working. > > > > > > Have you tried to completely delete the site-author/build/forrest-docs/ > > > directory. Should not be needed, but perhaps your forrestbot-built > > > docs have become corrupted somehow. > > > > Yes. I've tried forrest clean and manually deleted. > > Did you also manually delete the site-author/work directory? > That is the one that is giving you problems.
Yes. I've deleted both work and build directories. After the work directory is deleted, I can run through the sequence build.. deploy once and get success messages although nothing actually deploys. Running them a second time causes the errors described in this email. > > > > Because of the Authorization Fails error that I get towards the end I > > > > decided to see if I could manually update the site by committing a > > > > single set (pdf+html) of changes on a single document. That too > > > > failed because of "inconsistent line endings" -- maybe that > > > > authorization thing is masking a line-ending problem? Or, maybe I've > > > > got multiple problems? > > > > > > Would you please explain in more detail what you tried there. > > > I don't understand. Did you do a normal build with > > > cd site-author > > > forrest > > > cp build/site/index.html ../../forrest-site > > > cd ../../forrest-site > > > svn diff index.html > > > svn commit index.html > > > > No, I haven't tried a standard forrest site on my own. What I tried > > was committing what forrestbot had apparently already checked out in: > > "site-author\work\svn-deploy\forrest-docs\" > > Ah, now i see what you were doing. Was 'svn diff' showing > the changes that you would expect? For that specific file it was. It also "thinks" there are multiple other files that have changes that I wouldn't have expected to have been changed. Looking at the diff of those files, I can only gather that they are line ending changes because there aren't visibly any differences between old and new. > > > You should not be getting line-endings issues. > > > I will wait for your further detail above, then we > > > can investigate that issue. > > > > > > I just verified the "forrest-site" repository. There we some > > > with incorrect svn:eol-style problems and consequently > > > had line-endings issues. The "abs-linkmap" was one of those. > > > > > > More below ... > > > > > > > Any help would be appreciated, I've had this problem too long now... > > > > > > > > --tim > > > > > > > > ****************************************************** > > > > > > > > C:\src\apache-forrest-trunk-s\site-author>forrest -f publish.xml deploy > > > > -Ddeploy > > > > .svn.commit-message="another forrestbot attempt" > > > > > > Forget the "-Ddeploy ..." part, as it is busted. > > > > > > > Apache Forrest. Run 'forrest -projecthelp' to list options > > > > > > > > > > > > Buildfile: publish.xml > > > > > > > > deploy.svn: > > > > Copying 400 files to > > > > C:\src\apache-forrest-trunk-s\site-author\work\svn-deploy\f > > > > orrest-docs > > > > svn: warning: 'broken-links.xml' is already under version control > > > > svn: warning: 'forrest-issues.html' is already under version control > > > ... [ snip for brevity ] > > > > svn: warning: 'forrest-friday.html' is already under version control > > > > svn: warning: 'forrest-issues.pdf' is already under version control > > > > svn: warning: 'pluginDocs\plugins_0_70\index.pdf' is already under > > > > version contr > > > > ol > > > > svn: 'M > > > > pluginDocs\plugins_0_70\org.apache.forrest.plugin.internal.IMSManife > > > > st\repositoryCommand\getSCO\HowTo\repositoryURI\www.burrokeet.org\repositoryData > > > > ' is not a working copy > > > > > > I don't know what that is about. Those docs are not handled > > > by forrestbot nor the "site-author" build. The pluginDocs > > > have their own deployment mechanism. So this is supporting > > > my suggestion above to remove the site-author/build/forrest-docs/ > > > > Yeah, I have done that. Actually, in the many times that I've tried > > forrestbot, I've completely deleted and rechecked out the entire > > trunk. So cleanliness, I think, isn't likely an issue. > > Well i cannot explain why that IMSManifest stuff has been > touched. The "M" means locally modified. And it should not be. > > Another thing that i don't understand is that it seems that > every file has been added again. The first time I run through the sequence, the toadd file has only these IMSManifest files. Running through the second time has the numerous other files in there as well. Running svn status myself, not surprisingly, results in the same. > I just tried again myself by removing both site-author/build > and site-author/work directories then > forrest -f publish.xml build > forrest -f publish.xml deploy > > Nothing was deployed. I suppose that that is normal. I don't understand why this is normal. If it's really necessary to run through the sequence twice on a fresh site-author then we should add that to the doc. Can you explain more about why this is expected? I'd like to understand. > Then i did it again: > forrest -f publish.xml build > forrest -f publish.xml deploy > > Only the changed files were 'svn add' and deployed > as expected. You would have seen the commit email. I did. > For example, "forrest-friday.html" was not mentioned, > but i see that it was mentioned in your listing. > > > > > Result: 1 > > > > svn: Commit failed (details follow): > > > > svn: CHECKOUT of '/repos/asf/!svn/ver/332744/forrest/site/abs-linkmap': > > > > authoriz > > > > ation failed (https://svn.apache.org) > > > > > > > > BUILD FAILED > > > > C:\src\apache-forrest-trunk-s\tools\forrestbot\core\deploy.xml:157: > > > > com.alternat > > > > ecomputing.jsvn.command.CommandException: svn: Commit failed (details > > > > follow): > > > > svn: CHECKOUT of '/repos/asf/!svn/ver/332744/forrest/site/abs-linkmap': > > > > authoriz > > > > ation failed (https://svn.apache.org) > > > > > > I don't know what this is about. Lets wait on your further > > > info from above. > > > > Ok, I've given the further info you've asked for hopefully it's > > helpful. > > The main info that i was seeking was that you were able to > commit to the forrest/site repository. Try the manual method > described above. Or perhaps try tweaking an html doc in > site-author\work\svn-deploy\forrest-docs\ > and then 'svn commit' it. You've probably already seen, but I can manually commit to the site repo. > > I want to mention too that I've got a Linux (fedora core) > > box that is my file/print server at home and I've tried forrrestbot on > > it too to no avail -- I don't remember if the errors are exactly the > > same or not though. > > Hmmm, i wish that someone else would try it. Me too. I don't doubt though that I'm doing something wrong -- just can't figure out what it is. I ran through it again on my linux box and the issue is exactly the same as I've been describing so it doesn't appear to be a windows thing. --tim
