From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory
Date: Wed, 07 Mar 2018 20:18:00 -0000 [thread overview]
Message-ID: <fab9c762-6020-3084-dcbf-7a006a41ee58@dronecode.org.uk> (raw)
In-Reply-To: <b03fcc59d6ed4831b4f7c9a225d14466@merl.com>
On 07/03/2018 17:22, Robert Cohen wrote:
>>> I did get one postinstall script error:
>>>
>>> Package: _/libfontconfig-common
>>> fontconfig_dtd.sh exit code 2
>>>
>>> Here's the related error from setup.log.full, along with info on the command that ran just before that one:
>>>
>>> 2018/03/06 17:57:14 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.dash"
>>> Rebuilding info directory
>>> install-info: warning: no info dir entry in `/usr/share/info/latex2rtf.info.gz'
>>> 2018/03/06 17:57:31 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/fontconfig_dtd.sh"
>>> could not open /etc/xml/catalog for saving
>>> add command failed
>>> 2018/03/06 17:57:31 abnormal exit: exit code=2
>>>
>>> I looked in /etc/xml/, and the catalog file was there, containing the following:
>>>
>>> <?xml version="1.0"?>
>>> <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
>>> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>
>>>
>>> Is the error from fontconfig_dtd.sh something to be concerned about?
>>
>> This looks like a problem with the order postinstall steps are being
>> run, possibly due to a missing dependency
>>
>> Can you please provide the setup.log.full?
>
> Yes, attached is the setup.log.full file.
Thanks.
Yeah, this looks like an ordering problem between libxml2 and
libfontconfig-common.
> $ cat /etc/postinstall/fontconfig_dtd.sh
> if [ -x /usr/bin/xmlcatalog ] ; then
> /usr/bin/xmlcatalog --noout --add "system" "fonts.dtd" /usr/share/xml/fontconfig/fonts.dtd /etc/xml/catalog
> fi
>
> $ cat /etc/postinstall/libxml2.sh
> if test ! -f /etc/xml/catalog; then
> /bin/mkdir -p /etc/xml
> /usr/bin/xmlcatalog --noout --create /etc/xml/catalog
> fi
Not sure how to fix this.
I think there's no actual dependency of libfontconfig-common on
xmlcatalog, but we lack a triggering mechanism to say "run this script
when this other package is installed"
Yaakov?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-03-07 20:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 23:00 Robert Cohen
2018-03-03 23:54 ` Brian Inglis
2018-03-04 1:51 ` Robert Cohen
2018-03-04 2:16 ` Ken Brown
2018-03-04 2:32 ` Brian Inglis
2018-03-04 3:01 ` Robert Cohen
2018-03-04 3:11 ` Ken Brown
2018-03-04 4:01 ` Robert Cohen
2018-03-04 5:02 ` Brian Inglis
2018-03-04 5:26 ` Robert Cohen
2018-03-04 15:22 ` Ken Brown
2018-03-06 23:14 ` Jon Turney
2018-03-07 3:37 ` Robert Cohen
2018-03-07 12:15 ` Jon Turney
2018-03-07 20:09 ` Robert Cohen
[not found] ` <b03fcc59d6ed4831b4f7c9a225d14466@merl.com>
2018-03-07 20:18 ` Jon Turney [this message]
2018-03-22 21:56 ` Ken Brown
2018-03-23 16:54 ` Achim Gratz
2018-03-23 21:10 ` Ken Brown
2018-03-24 1:05 ` 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=fab9c762-6020-3084-dcbf-7a006a41ee58@dronecode.org.uk \
--to=jon.turney@dronecode.org.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).