On 2021-08-22 16:58, Ken Brown via Cygwin-apps wrote:
On 8/22/2021 6:38 PM, Ken Brown via Cygwin-apps wrote:
On 8/22/2021 5:57 PM, Brian Inglis wrote:
On 2021-08-22 09:33, Brian Inglis wrote:
On 2021-08-22 09:15, Jon Turney wrote:
On 22/08/2021 01:48, Brian Inglis wrote:
Any way to see if there is anything useful in scallywag #160
(3181) fontconfig run 1154600337 build_requires setup
/var/log/setup.log.full without hacking and pushing
fontconfig.cygport?
https://github.com/cygwin/scallywag/actions/runs/1154600337/workflow
Trying to build updated fontconfig (to see if continual cache
creation issue has been resolved, or analyze and hopefully debug
that issue to remove or patch the cause, then ITA), but getting
weird build issues.
Trying scallywag playground, but it's also having problems
installing prereq texlive-collection-htmlxml, which pulls in other
packages including texlive-collection-formatsextra, which need
built by
/etc/postinstall/zp_texlive_finish.dash, which is failing
somewhere with exit code 2 - not a lot of detail!
I've tweaked scallywag so setup.log.full is also preserved in the
builddir artefact.
This might now contain something useful if the post-install script
is emitting an error.
Thanks Jon,
I'll rerun and check, and see if I can mitigate it in cygport under
scallywag.
Thanks again Jon,
That allowed me to track it down: it looks like the issue is marvosym:
docbook-utils -> texlive-collection-htmlxml ->
texlive-collection-plaingeneric -> marvosym ->
texlive-collection-fontsrecommended
but texlive-collection-plaingeneric does not require
texlive-collection-fontsrecommended, so it looks like that may have
to be explicitly requested in the cygport build.
Opinion sought from Ken Brown!
$ zfgrep marvosym
/etc/setup/texlive-collection-{plaingeneric,fontsrecommended}.lst.gz
/etc/setup/texlive-collection-plaingeneric.lst.gz:usr/share/texmf-dist/tex4ht/ht-fonts/alias/marvosym/
/etc/setup/texlive-collection-plaingeneric.lst.gz:usr/share/texmf-dist/tex4ht/ht-fonts/alias/marvosym/fmvri8x.htf
/etc/setup/texlive-collection-plaingeneric.lst.gz:usr/share/texmf-dist/tex4ht/ht-fonts/unicode/marvosym/
/etc/setup/texlive-collection-plaingeneric.lst.gz:usr/share/texmf-dist/tex4ht/ht-fonts/unicode/marvosym/fmvr8x.htf
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/afm/public/marvosym/
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/afm/public/marvosym/marvosym.afm
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/map/dvips/marvosym/
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/map/dvips/marvosym/marvosym.map
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/tfm/public/marvosym/
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/tfm/public/marvosym/umvs.tfm
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/truetype/public/marvosym/
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/truetype/public/marvosym/marvosym.ttf
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/type1/public/marvosym/
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/fonts/type1/public/marvosym/marvosym.pfb
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/tex/latex/marvosym/
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/tex/latex/marvosym/marvosym.sty
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/texmf-dist/tex/latex/marvosym/umvs.fd
/etc/setup/texlive-collection-fontsrecommended.lst.gz:usr/share/tlpkg/tlpobj/marvosym.tlpobj
Sorry, but I need more detail. I'd be very surprised if
texlive-collection-fontsrecommended is needed in order to rebuild
formats, but maybe I'm missing something. Please start from the
beginning and say exactly what you're doing and exactly how
zp_texlive_finish.dash is failing.
OK, your later messages explain it better. I'll have to look at
texlive-collection-formatsextra; it's possible that it needs to require
texlive-collection-fontsrecommended. But a better solution to your
immediate problem would be for someone to look at docbook-utils and see
whether it really needs texlive-collection-formatsextra. It currently
requires the obsolete texlive-collection-htmlxml, which pulls in a lot
of other packages, probably unnecessarily in most cases. See
https://cygwin.com/packages/summary/texlive-collection-htmlxml.html
That would require a TeX-y who knows the TeX relationships of the files.
From what I can see jadetex and pdfjadtex are used by docbook-utils, so
whatever they need to be built and used.
From docbook-utils /usr/doc/html/docbook-utils-0.6.14/jw.html:
"The jw shell script allows to convert a DocBook file (or some other
SGML-based format) to other formats (including HTML, RTF, PS and PDF)
with an easy-to-understand syntax. It hides most of Jade's or OpenJade
complexity and adds comfortable features.
Other scripts like docbook2html, docbook2rtf or docbook2ps provide
different ways of calling jw that might be easier to remember.
For the moment, jw does not handle XML, but only SGML.
This utility assumes that several other components are installed. The
list includes:
the ISO character entities for SGML
James Clark's DSSSL engine, jade, or an equivalent parser like OpenJade
the DocBook DTD from the OASIS consortium
Norman Walsh's DocBook modular style sheets (or some other set of DSSSL
style sheets)
Sebastian Rahtz's jadetex set of TeX macros for jade (for backends
intended to "printing" formats like PDF, RTF or PostScript)
A perl interpreter (for backends that use perl)
SGMLSpm from CPAN (for backends that use sgmls)
Lynx HTML browser (for the txt backend)."
I don't know if that gives anyone TeX-y enough information to say which
more recent dependencies are necessary, although previous releases of
htmlxml required fontsrecommended, and none of its dependencies now do,
so it should be required by one or more of those.
It looks like some tools are last century and others more than a decade
old, so nothing is likely to happen with those legacy projects.
The source documents could do with being converted from legacy SGML, TeX
formats to something modern like restructured text, and modern tools
used to generate output formats if required, although browser extensions
provide readable output from many modern formats.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
