Обсуждение: PDF Builds on borka (Debian/stretch) broken - 9.6

Greetings,

While trying to do the PDF builds on borka for 9.6 for tomorrow's
release, I'm getting:

openjade  -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d ./stylesheet.dsl -t tex -V
tex-backend-i output-print -i include-index -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf postgres.sgml
 
openjade:./stylesheet.dsl:670:9:E: flow object not accepted by port; only display flow objects accepted
Makefile:180: recipe for target 'postgres-A4.tex-pdf' failed
make: *** [postgres-A4.tex-pdf] Segmentation fault
make: *** Deleting file 'postgres-A4.tex-pdf'

The 10.2 build worked (though required me to up the memory in the box;
note that the above error is even after the memory increase and does not
appear to be a memory allocation issue anyway).

Any idea what's happening here..?  The interwebs seem to indicate that
it might be something to do with glossary and I'm wondering if we've
tripped over whatever that internal limit of openjade was, again, and,
if so, if there's anything we can do about it.

Obviously would be great to get this fixed for tomorrow's release, so if
you're able to help at all, it would be appreciated.

I'm going to try doing the builds for 9.5, et al, next.

Thanks!

Stephen

Stephen Frost <sfrost@snowman.net> writes:
> While trying to do the PDF builds on borka for 9.6 for tomorrow's
> release, I'm getting:

> openjade  -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d ./stylesheet.dsl -t tex -V
tex-backend-i output-print -i include-index -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf postgres.sgml 
> openjade:./stylesheet.dsl:670:9:E: flow object not accepted by port; only display flow objects accepted
> Makefile:180: recipe for target 'postgres-A4.tex-pdf' failed
> make: *** [postgres-A4.tex-pdf] Segmentation fault
> make: *** Deleting file 'postgres-A4.tex-pdf'

Bleah.

We've seen this before, eg
https://www.postgresql.org/message-id/51CB39BD.8020205%40pgexperts.com

and the conclusion seemed to be that it was from having the wrong version
of openjade installed.  Was borka upgraded recently?

            regards, tom lane

Tom,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > While trying to do the PDF builds on borka for 9.6 for tomorrow's
> > release, I'm getting:
>
> > openjade  -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d ./stylesheet.dsl -t tex -V
tex-backend-i output-print -i include-index -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf postgres.sgml 
> > openjade:./stylesheet.dsl:670:9:E: flow object not accepted by port; only display flow objects accepted
> > Makefile:180: recipe for target 'postgres-A4.tex-pdf' failed
> > make: *** [postgres-A4.tex-pdf] Segmentation fault
> > make: *** Deleting file 'postgres-A4.tex-pdf'
>
> Bleah.
>
> We've seen this before, eg
> https://www.postgresql.org/message-id/51CB39BD.8020205%40pgexperts.com
>
> and the conclusion seemed to be that it was from having the wrong version
> of openjade installed.  Was borka upgraded recently?

Well, not recently, but it was upgraded to stretch a while back, yes.
It's got:

ii  openjade                         1.4devel1-21.3+b1 amd64        Implementation of the DSSSL language

I'm not seeing any alternatives for it immediately.

Thanks!

Stephen

Tom,

* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > While trying to do the PDF builds on borka for 9.6 for tomorrow's
> > release, I'm getting:
>
> > openjade  -D . -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d ./stylesheet.dsl -t tex -V
tex-backend-i output-print -i include-index -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf postgres.sgml 
> > openjade:./stylesheet.dsl:670:9:E: flow object not accepted by port; only display flow objects accepted
> > Makefile:180: recipe for target 'postgres-A4.tex-pdf' failed
> > make: *** [postgres-A4.tex-pdf] Segmentation fault
> > make: *** Deleting file 'postgres-A4.tex-pdf'
>
> Bleah.
>
> We've seen this before, eg
> https://www.postgresql.org/message-id/51CB39BD.8020205%40pgexperts.com
>
> and the conclusion seemed to be that it was from having the wrong version
> of openjade installed.  Was borka upgraded recently?

Looks like Nov 15 (which I believe is when the stretch upgrade was done)
it was upgraded:

2017-11-15 17:38:55 upgrade openjade:amd64 1.4devel1-21.1 1.4devel1-21.3+b1

That doesn't look like a terribly large version bump to me tho..

Thanks!

Stephen

Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> We've seen this before, eg
>> https://www.postgresql.org/message-id/51CB39BD.8020205%40pgexperts.com
>> and the conclusion seemed to be that it was from having the wrong version
>> of openjade installed.  Was borka upgraded recently?

> Looks like Nov 15 (which I believe is when the stretch upgrade was done)
> it was upgraded:
> 2017-11-15 17:38:55 upgrade openjade:amd64 1.4devel1-21.1 1.4devel1-21.3+b1
> That doesn't look like a terribly large version bump to me tho..

Digging around further in our archives, it seems that this bug is specific
to openjade 1.4devel, and 1.3.x works fine.  But if borka was not running
1.3 before then it's hard to know what to make of it.  Since this is the
first report of this failure since 2013, I'd sort of thought the problem
was gone, but evidently not :-(

Another line of thought is that it might be an interaction between
particular versions of openjade and particular versions of the dsssl
style sheets.  Were the latter upgraded?

            regards, tom lane

On 2/7/18 17:21, Stephen Frost wrote:
> Looks like Nov 15 (which I believe is when the stretch upgrade was done)
> it was upgraded:
> 
> 2017-11-15 17:38:55 upgrade openjade:amd64 1.4devel1-21.1 1.4devel1-21.3+b1
> 
> That doesn't look like a terribly large version bump to me tho..

You probably had the openjade1.3 package installed, and maybe it got
deleted or the alternative uninstalled during the upgrade.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Peter,

* Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
> On 2/7/18 17:21, Stephen Frost wrote:
> > Looks like Nov 15 (which I believe is when the stretch upgrade was done)
> > it was upgraded:
> >
> > 2017-11-15 17:38:55 upgrade openjade:amd64 1.4devel1-21.1 1.4devel1-21.3+b1
> >
> > That doesn't look like a terribly large version bump to me tho..
>
> You probably had the openjade1.3 package installed, and maybe it got
> deleted or the alternative uninstalled during the upgrade.

Thanks for that, yes, that got uninstalled but I've now re-installed it
and the PDF builds for 9.6-9.3 are working and will be included in
today's release.

Thanks again!

Stephen