From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: postinstall: fontconfig abnormal exit
Date: Tue, 8 Sep 2020 13:03:09 +0100 [thread overview]
Message-ID: <DB7PR02MB3996556499024C3FD639FF83E7290@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <DB6PR03MB3013DDDB803E3E4B8EF8E935A4290@DB6PR03MB3013.eurprd03.prod.outlook.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 977 bytes --]
On 08/09/2020 07:43, Fergus Daly via Cygwin wrote:
> Sorry if this has been asked 4 million times already.
> During postinstall, both at ground-zero installation and at every update thereafter, and for both Cygwin-32 and -64,
> (both using the appropriate setup-x86[_64].exe) I get:
> running: {pathToCygwin}\bin\bash.exe --norc --noprofile "/etc/postinstall/fontconfig_dtd.sh"
> abnormal exit: exit code=2
> Is there something that can be done to address this "error", if that is what it is, or is it just a quirk of setup?
> Thank you!
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
I have this issue too, at least on first install. I just ignored it and
assumed it wasn't a big deal, but it would be nice to know why this
happens if others experience it too.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-08 12:03 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 [this message]
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
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=DB7PR02MB3996556499024C3FD639FF83E7290@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).