You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Tim Williams <wi...@gmail.com> on 2005/11/29 22:31:09 UTC
forrestbot problems
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.
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?
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"
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
svn: warning: 'tools\forrestbot-web-interface.html' is already under version con
trol
svn: warning: 'tools\eclipse.html' is already under version control
svn: warning: 'tools\xxe.html' is already under version control
svn: warning: 'tools\forrestbar.html' is already under version control
svn: warning: 'tools\forrestbot.html' is already under version control
svn: warning: 'abs-menulinks' is already under version control
svn: warning: 'committed.html' is already under version control
svn: warning: 'dtdx\document-v20.html' is already under version control
svn: warning: 'dtdx\document-v12.html' is already under version control
svn: warning: 'dtdx\document-v13.html' is already under version control
svn: warning: 'dtdx\document-v20.pdf' is already under version control
svn: warning: 'dtdx\document-v12.pdf' is already under version control
svn: warning: 'dtdx\document-v13.pdf' is already under version control
svn: warning: 'dtdx\dtd-docs.html' is already under version control
svn: warning: 'skin\print.css' is already under version control
svn: warning: 'skin\images\rc-t-l-5-1header-2tab-selected-3tab-selected.png' is
already under version control
svn: warning: 'skin\images\rc-t-l-5-1header-2searchbox-3searchbox.png' is alread
y under version control
svn: warning: 'skin\images\rc-t-r-5-1header-2tab-selected-3tab-selected.png' is
already under version control
svn: warning: 'skin\images\rc-t-l-5-1header-2tab-unselected-3tab-unselected.png'
is already under version control
svn: warning: 'skin\images\rc-t-r-5-1header-2searchbox-3searchbox.png' is alread
y under version control
svn: warning: 'skin\images\rc-t-r-5-1header-2tab-unselected-3tab-unselected.png'
is already under version control
svn: warning: 'skin\images\rc-b-l-15-1body-2menu-3menu.png' is already under ver
sion control
svn: warning: 'skin\images\rc-b-r-15-1body-2menu-3menu.png' is already under ver
sion control
svn: warning: 'skin\images\rc-t-r-15-1body-2menu-3menu.png' is already under ver
sion control
svn: warning: 'skin\images\rc-b-r-5-1header-2tab-selected-3tab-selected.png' is
already under version control
svn: warning: 'skin\images\chapter_open.gif' is already under version control
svn: warning: 'skin\screen.css' is already under version control
svn: warning: 'skin\basic.css' is already under version control
svn: warning: 'docs_0_60\howto\howto-howto.html' is already under version contro
l
svn: warning: 'docs_0_60\howto\howto-asf-mirror.html' is already under version c
ontrol
svn: warning: 'docs_0_60\howto\bugzilla-patch\howto-bugzilla-patch.html' is alre
ady under version control
svn: warning: 'docs_0_60\howto\howto-pdf-tab.html' is already under version cont
rol
svn: warning: 'docs_0_60\linking.pdf' is already under version control
svn: warning: 'docs_0_60\your-project.html' is already under version control
svn: warning: 'docs_0_60\searching.html' is already under version control
svn: warning: 'docs_0_60\cap.html' is already under version control
svn: warning: 'docs_0_60\project-sitemap.html' is already under version control
svn: warning: 'docs_0_60\your-project.pdf' is already under version control
svn: warning: 'docs_0_60\faq.html' is already under version control
svn: warning: 'docs_0_60\catalog.html' is already under version control
svn: warning: 'docs_0_60\sitemap-ref.html' is already under version control
svn: warning: 'docs_0_60\upgrading_06.html' is already under version control
svn: warning: 'docs_0_60\validation.html' is already under version control
svn: warning: 'docs_0_60\linking.html' is already under version control
svn: warning: 'docs_0_60\build.html' is already under version control
svn: warning: 'docs_0_60\forrest-contract.html' is already under version control
svn: warning: 'docs_0_60\todo.html' is already under version control
svn: warning: 'docs_0_60\compliance.html' is already under version control
svn: warning: 'plan\index.pdf' is already under version control
svn: warning: 'plan\index.html' is already under version control
svn: warning: 'abs-linkmap' is already under version control
svn: warning: 'contrib.html' is already under version control
svn: warning: 'body-index.html' is already under version control
svn: warning: 'committed-1.png' is already under version control
svn: warning: 'docs_0_70\libre-intro.html' is already under version control
svn: warning: 'docs_0_70\upgrading_07.html' is already under version control
svn: warning: 'docs_0_70\howto\howto-asf-mirror.html' is already under version c
ontrol
svn: warning: 'docs_0_70\howto\cvs-ssh\howto-cvs-ssh.html' is already under vers
ion control
svn: warning: 'docs_0_70\howto\howto-view-dsl.html' is already under version con
trol
svn: warning: 'docs_0_70\howto\howto-corner-images.html' is already under versio
n control
svn: warning: 'docs_0_70\howto\howto-howto.html' is already under version contro
l
svn: warning: 'docs_0_70\howto\howto-custom-html-source.html' is already under v
ersion control
svn: warning: 'docs_0_70\howto\howto-buildPlugin.html' is already under version
control
svn: warning: 'docs_0_70\howto\howto-view-install.html' is already under version
control
svn: warning: 'docs_0_70\howto\howto-forrest-from-maven.html' is already under v
ersion control
svn: warning: 'docs_0_70\howto\howto-view-contracts.html' is already under versi
on control
svn: warning: 'docs_0_70\howto\howto-pdf-tab.html' is already under version cont
rol
svn: warning: 'docs_0_70\linking.pdf' is already under version control
svn: warning: 'docs_0_70\your-project.html' is already under version control
svn: warning: 'docs_0_70\searching.html' is already under version control
svn: warning: 'docs_0_70\cap.html' is already under version control
svn: warning: 'docs_0_70\project-sitemap.html' is already under version control
svn: warning: 'docs_0_70\your-project.pdf' is already under version control
svn: warning: 'docs_0_70\faq.html' is already under version control
svn: warning: 'docs_0_70\catalog.html' is already under version control
svn: warning: 'docs_0_70\changes.rss' is already under version control
svn: warning: 'docs_0_70\sitemap-ref.html' is already under version control
svn: warning: 'docs_0_70\validation.html' is already under version control
svn: warning: 'docs_0_70\linking.html' is already under version control
svn: warning: 'docs_0_70\primer.html' is already under version control
svn: warning: 'docs_0_70\forrest-contract.html' is already under version control
svn: warning: 'docs_0_70\build.html' is already under version control
svn: warning: 'docs_0_70\primer.pdf' is already under version control
svn: warning: 'docs_0_70\todo.html' is already under version control
svn: warning: 'docs_0_70\compliance.html' is already under version control
svn: warning: 'mirrors.html' is already under version control
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
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)
Total time: 1 minute 45 seconds
Re: forrestbot problems
Posted by Ross Gardler <rg...@apache.org>.
Ross Gardler 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.
>>
>> 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?
>
>
> I'm afraid to say I have never tried updating using the forrestbot -
> sorry David.
>
> However, your line endings problem rings a bell and I note you are on
> Windows. When I was doing the code to auto-deploy the plugin docs I got
> the same/similar problem:
>
> http://marc.theaimsgroup.com/?l=forrest-dev&m=110468471529182&w=2
>
> There is currently a workaround in place that fixes the problem, but we
> could really do with resolving this issue. Especially now that it seems
> to have arisen again in a different context.
>
> There is an issue for this at http://issues.apache.org/jira/browse/FOR-492
Re-reading the above linked thread I feel fairly sure this is the same
issue. The last mail in that thread links to a XALANJ issue David
discovered:
David says:
I don't know if this is related, but thanks Google and mail-archive.com:
"line endings" "xsl:comment" ...
http://issues.apache.org/jira/browse/XALANJ-656
"<xsl:copy> introduces inappropriate line-end characters processing
comments".
Reading that issue it looks like it is the cause of our problem. I would
also suggest the fix in the plugins build file (fix line endings using
an ANT task) would be a suitable workaround here.
Ross
Ross
Re: forrestbot problems
Posted by Ross Gardler <rg...@apache.org>.
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.
>
> 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?
I'm afraid to say I have never tried updating using the forrestbot -
sorry David.
However, your line endings problem rings a bell and I note you are on
Windows. When I was doing the code to auto-deploy the plugin docs I got
the same/similar problem:
http://marc.theaimsgroup.com/?l=forrest-dev&m=110468471529182&w=2
There is currently a workaround in place that fixes the problem, but we
could really do with resolving this issue. Especially now that it seems
to have arisen again in a different context.
There is an issue for this at http://issues.apache.org/jira/browse/FOR-492
Ross
Re: forrestbot problems
Posted by David Crossley <cr...@apache.org>.
Tim Williams wrote:
> >
> > 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.
Would you please provide an example of a file that has
such problems. If it is diffs in certain comments,
then we know that problem (Ross mentioned it in other
mail in this thread).
Also can you double-check that your Subversion configuration
is okay:
http://www.apache.org/dev/version-control.html#https-svn
> > > > > 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.
Sorry i have no idea. That is why i said "i suppose".
> > 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.
Good, so no permissions issues.
> > > 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.
Oh wow, that is really strange.
-David
Re: forrestbot problems
Posted by Ross Gardler <rg...@apache.org>.
Tim Williams wrote:
> On 12/5/05, David Crossley <cr...@apache.org> wrote:
>
>>Ross Gardler wrote:
>>
>>>Tim Williams wrote:
>>>
>>>>David Crossley wrote:
>>>>
>>>>>Tim Williams wrote:
>>>>>
>>>>>>David Crossley wrote:
>>>
>>>...
>>>
>>>
>>>>>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.
>>>
>>>I just tried it (Windows XP + Cygwin). I get the same problem.
>>>
>>>I've not seen either of you comment on the Xalan issue that we have come
>>>up against before (see my earlier mails in this thread). Now that I have
>>>done a test I can confirm that I am seeing the same effects, at least
>>>with respect to the inconsistent line endings.
>>>
>>>Top see the problem, just open up a generated file and you'll find that
>>>comments have different line endings to all other content. For example:
>>>
>>><div id="top">^M
>>><!--+
>>> |breadtrail
>>> +-->^M
>>><div class="breadtrail">^M
>>
>>So Tim is this the issue that you are seeing
>>or is it something else?
>>
>>-David
>>
>
>
> That does appear to be why all of the files have changed. I'm not
> sure if there's more than one issue or what though. I don't know how
> this could result in the authorization failure error I was getting.
To fix the above we need to use the FixCRLF task in ANT [1], at last
until the bug in Xalan is fixed. I used this in the plugin build.xml to
fix the same problem.
I have no idea about the authorisation stuff I;m afraid.
Ross
[1] http://ant.apache.org/manual/CoreTasks/fixcrlf.html
Re: forrestbot problems
Posted by Tim Williams <wi...@gmail.com>.
On 12/5/05, David Crossley <cr...@apache.org> wrote:
> Ross Gardler wrote:
> > Tim Williams wrote:
> > >David Crossley wrote:
> > >>Tim Williams wrote:
> > >>>David Crossley wrote:
> >
> > ...
> >
> > >>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.
> >
> > I just tried it (Windows XP + Cygwin). I get the same problem.
> >
> > I've not seen either of you comment on the Xalan issue that we have come
> > up against before (see my earlier mails in this thread). Now that I have
> > done a test I can confirm that I am seeing the same effects, at least
> > with respect to the inconsistent line endings.
> >
> > Top see the problem, just open up a generated file and you'll find that
> > comments have different line endings to all other content. For example:
> >
> > <div id="top">^M
> > <!--+
> > |breadtrail
> > +-->^M
> > <div class="breadtrail">^M
>
> So Tim is this the issue that you are seeing
> or is it something else?
>
> -David
>
That does appear to be why all of the files have changed. I'm not
sure if there's more than one issue or what though. I don't know how
this could result in the authorization failure error I was getting.
--tim
Re: forrestbot problems
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Tim Williams wrote:
> >David Crossley wrote:
> >>Tim Williams wrote:
> >>>David Crossley wrote:
>
> ...
>
> >>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.
>
> I just tried it (Windows XP + Cygwin). I get the same problem.
>
> I've not seen either of you comment on the Xalan issue that we have come
> up against before (see my earlier mails in this thread). Now that I have
> done a test I can confirm that I am seeing the same effects, at least
> with respect to the inconsistent line endings.
>
> Top see the problem, just open up a generated file and you'll find that
> comments have different line endings to all other content. For example:
>
> <div id="top">^M
> <!--+
> |breadtrail
> +-->^M
> <div class="breadtrail">^M
So Tim is this the issue that you are seeing
or is it something else?
-David
Re: forrestbot problems
Posted by Ross Gardler <rg...@apache.org>.
Tim Williams wrote:
> On 11/30/05, David Crossley <cr...@apache.org> wrote:
>
>>Tim Williams wrote:
>>
>>>David Crossley wrote:
...
>>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.
I just tried it (Windows XP + Cygwin). I get the same problem.
I've not seen either of you comment on the Xalan issue that we have come
up against before (see my earlier mails in this thread). Now that I have
done a test I can confirm that I am seeing the same effects, at least
with respect to the inconsistent line endings.
Top see the problem, just open up a generated file and you'll find that
comments have different line endings to all other content. For example:
<div id="top">^M
<!--+
|breadtrail
+-->^M
<div class="breadtrail">^M
Ross
Re: forrestbot problems
Posted by Tim Williams <wi...@gmail.com>.
On 11/30/05, David Crossley <cr...@apache.org> 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
Re: forrestbot problems
Posted by David Crossley <cr...@apache.org>.
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.
> > > 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?
> > 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.
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.
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.
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.
> 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.
-David
Re: forrestbot problems
Posted by Tim Williams <wi...@gmail.com>.
On 11/29/05, David Crossley <cr...@apache.org> 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.
> > 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\"
> 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.
> > 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. 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.
--tim
Re: forrestbot problems
Posted by David Crossley <cr...@apache.org>.
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.
> 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
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/
> 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.
-David