<html dir="ltr"><head></head><body style="text-align: left; direction: ltr; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" bgcolor="#ffffff" text="#2e3436" link="#1b6acb" vlink="#2e3436"><div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Hi Michalis,</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"> </div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">I'm sorry that I could not work on this due to urgent matters from real life (including sad family event).</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">So I think pushing to bulleseye is now impossible. But I'll try to have at least backports up to date.</div></div><div><span><pre><pre>-- <br></pre>Cheers,
Abou Al Montacir
</pre></span></div><div><br></div><div>On Fri, 2021-02-26 at 03:07 +0100, Michalis Kamburelis wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>1. PasDoc warnings about inability to parse $if -- these will</pre><pre>disappear if you use PasDoc 0.16.0. You can also just ignore them (to</pre><pre>not make CGE update in Debian blocked by PasDoc update in Debian).</pre><pre>They are indeed just warnings, and should not cause PasDoc to exit</pre><pre>with non-zero status. They occur so often, because the construction</pre><pre>with $if is used within castleconf.inc, which is included in all the</pre><pre>units.</pre><pre><br></pre><pre>2. PasDoc warnings about invalid links -- my mistake. Take this patch:</pre><a href="https://github.com/castle-engine/castle-engine/commit/7d62f9bd5b97d88ee2fae248eb963c0af1c0c5d1"><pre>https://github.com/castle-engine/castle-engine/commit/7d62f9bd5b97d88ee2fae248eb963c0af1c0c5d1</pre></a><pre><br></pre><pre>. Or simply ignore them, they should not cause PasDoc to exit with</pre><pre>non-zero status. I added a TODO for myself to improve my Jenkins job,</pre><pre>to fail in case of any warnings, so I will spot them immediately in</pre><pre>the future.</pre><pre><br></pre><pre>3. There is 1 error that actually causes PasDoc to exit with non-zero status:</pre><pre><br></pre><pre> Warning[2]: Error EPasDoc: ./x3d/x3dnodes_prototypes.inc(984):</pre><pre>Unexpected reserved word "end" while parsing unit x3dnodes.pas,</pre><pre>continuing...</pre><pre><br></pre><pre>This is a bug in PasDoc 0.15.0. It is fixed in PasDoc 0.16.0. If you</pre><pre>want to build API docs with older PasDoc 0.15.0, please apply the</pre><pre>attached patch fix-for-pasdoc.0.15.0.patch (it removes a code that is</pre><pre>in practice unused).</pre><pre><br></pre><pre>Regards,</pre><pre>Michalis</pre><pre><br></pre></blockquote></body></html>