From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: scallywag zp_texlive_finish.dash failing exit code 2 rebuilding installed formats
Date: Sun, 22 Aug 2021 18:58:42 -0400 [thread overview]
Message-ID: <2e8d1505-7a3b-2282-ebaa-fc4180a8aa68@cornell.edu> (raw)
In-Reply-To: <86207a16-113c-517f-8503-27239c2fdd5d@cornell.edu>
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
Ken
next prev parent reply other threads:[~2021-08-22 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 0:48 Brian Inglis
2021-08-22 15:15 ` Jon Turney
2021-08-22 15:33 ` Brian Inglis
2021-08-22 21:57 ` Brian Inglis
2021-08-22 22:38 ` Ken Brown
2021-08-22 22:58 ` Ken Brown [this message]
2021-08-23 18:46 ` Brian Inglis
2021-08-23 21:08 ` Ken Brown
2021-08-24 0:26 ` Brian Inglis
2021-08-24 14:57 ` Ken Brown
2021-08-24 17:17 ` Brian Inglis
2021-08-22 22:20 ` /etc/postinstall/zp_texlive_finish.dash fails missing marvosysm.sty Brian Inglis
2021-08-22 22:26 ` Brian Inglis
2021-08-22 15:21 ` scallywag zp_texlive_finish.dash failing exit code 2 rebuilding installed formats Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e8d1505-7a3b-2282-ebaa-fc4180a8aa68@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).