From: Fergus Daly <fergusd84@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: postinstall: fontconfig abnormal exit
Date: Fri, 11 Sep 2020 07:22:26 +0000 [thread overview]
Message-ID: <VI1PR03MB3022EBE68767183BCA4889ECA4240@VI1PR03MB3022.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <20200910230426.5811f3e8@quarternote>
> On 2020-09-10 04:57, Fergus Daly via Cygwin wrote:
> >>>> Sorry if this has been asked 4 million times already.
> >
> >>> $ head /etc/postinstall/{fontconfig_dtd,libxml2}.*
> >> ==> /etc/postinstall/fontconfig_dtd.sh.done <==
> hmmm. i don't understand exactly what this thread is about, but i do know that on my latest fresh install of cygwin,
> the fontconfig_dtd install is claiming an error at the end.
> is this related to that ?
Exactly. On first setup and all subsequent updates this post-installation error recurs.
The cure described depends on the presence of several files including one that the script creates if necessary.
PS Before I enlisted help to cure this glitch "properly", I found it and its recurrence sufficiently intrusive to become an annoyance.
Since nothing was obviously broken I guessed that nothing further would be broken by artificially achieving the post-installation
sequence as follows:
$ mv /etc/postinstall/fontconfig_dtd.sh /etc/postinstall/fontconfig_dtd.sh.done
And so it transpired: nothing awful seemed to happen, or fail to happen, as a consequence of this "fix"; and the error msg stopped.
next prev parent reply other threads:[~2020-09-11 7:22 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 [this message]
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
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=VI1PR03MB3022EBE68767183BCA4889ECA4240@VI1PR03MB3022.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.com \
--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).