From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: postinstall: fontconfig abnormal exit
Date: Fri, 11 Sep 2020 15:47:14 -0400 [thread overview]
Message-ID: <ee4d59c7-00d3-a2e6-fa13-04622ed8391f@cornell.edu> (raw)
In-Reply-To: <06e9cf44-8cc8-267e-12b3-e8a866a01c80@gmail.com>
On 9/11/2020 10:41 AM, Marco Atzeri via Cygwin wrote:
> On 11.09.2020 15:12, Ken Brown via Cygwin wrote:
>> On 9/11/2020 7:31 AM, Marco Atzeri via Cygwin wrote:
>>> On 11.09.2020 10:32, Hamish McIntyre-Bhatty via Cygwin wrote:
>>>> On 11/09/2020 08:22, Fergus Daly via Cygwin wrote:
>>>>>> On 2020-09-10 04:57, Fergus Daly via Cygwin wrote:
>>>>>>>>>> Sorry if this has been asked 4 million times already.
>
>>>
>>> Installing just base+fontconfig is not providing any error,
>>> so it must be an interaction of fontconfig with some other package
>>
>> You can reproduce the problem by doing a fresh install and choosing
>> libfontconfig-common and libxml2. setup.log.full shows
>>
>> running: C:\cygwin64temp\bin\bash.exe --norc --noprofile
>> "/etc/postinstall/fontconfig_dtd.sh"
>> could not open /etc/xml/catalog for saving
>>
>> Marco, libxml2 used to have a postinstall script that would create
>> /etc/xml/catalog:
>>
>> $ cat /etc/postinstall/libxml2.sh.done
>> if test ! -f /etc/xml/catalog; then
>> /bin/mkdir -p /etc/xml
>> /usr/bin/xmlcatalog --noout --create /etc/xml/catalog
>> fi
>>
>> But this seems to have disappeared from the most recent release.
>
> noted.
> libxml2-2.9.10-2 on the build stage
Unfortunately, this doesn't yet fix the problem with fontconfig_dtd.sh. The
latter will now succeed if it is run after libxml2.sh, but not if it is run
first. I'm not aware of any way to force setup to run one postinstall script
before another. So maybe fontconfig_dtd.sh should be modified to include the
contents of libxml2.sh, like this:
$ cat fontconfig_dtd.sh
if [ -x /usr/bin/xmlcatalog ] ; then
if [ ! -f /etc/xml/catalog ] ; then
/bin/mkdir -p /etc/xml
/usr/bin/xmlcatalog --noout --create /etc/xml/catalog
fi
/usr/bin/xmlcatalog --noout --add "system" "fonts.dtd"
/usr/share/xml/fontconfig/fonts.dtd /etc/xml/catalog
fi
I can do a non-maintainer update of fontconfig that makes this change if people
agree that it's a good idea.
Ken
next prev parent reply other threads:[~2020-09-11 19:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 6:43 Fergus Daly
2020-09-08 12:03 ` Hamish McIntyre-Bhatty
2020-09-08 14:16 ` Andrey Repin
2020-09-08 15:18 ` Fergus Daly
2020-09-08 16:14 ` Brian Inglis
2020-09-10 5:23 ` Fergus Daly
2020-09-10 5:35 ` Andrey Repin
2020-09-10 10:57 ` Fergus Daly
2020-09-10 14:40 ` Brian Inglis
2020-09-11 6:04 ` briand
2020-09-11 7:22 ` Fergus Daly
2020-09-11 8:32 ` Hamish McIntyre-Bhatty
2020-09-11 11:31 ` Marco Atzeri
2020-09-11 13:12 ` Ken Brown
2020-09-11 14:41 ` Marco Atzeri
2020-09-11 19:47 ` Ken Brown [this message]
2020-09-11 20:30 ` Achim Gratz
2020-09-11 21:13 ` Ken Brown
2020-09-12 5:18 ` Brian Inglis
2020-09-12 12:56 ` Ken Brown
2021-07-20 17:00 ` Brian Inglis
2021-07-21 19:26 ` Ken Brown
2021-07-23 3:37 ` Brian Inglis
2020-09-12 6:08 ` ASSI
2020-09-13 16:53 ` Ken Brown
2020-09-16 8:42 ` Fergus Daly
2020-09-12 18:16 ` Andrey Repin
2020-09-14 15:47 ` Hamish McIntyre-Bhatty
2020-09-11 13:18 ` Fergus Daly
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=ee4d59c7-00d3-a2e6-fa13-04622ed8391f@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@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).