From: "Mark McGregor" <mark.mcgregor@gmx.de>
To: cygwin@cygwin.com
Subject: zp_fontconfig_cache_1.sh exit code 2
Date: Sun, 12 Jun 2016 22:32:00 -0000 [thread overview]
Message-ID: <trinity-f44febaf-a656-4566-b42a-bcccd2e6123a-1465767160468@3capp-gmx-bs72> (raw)
... and after one more installation, I get exit code 1. Don't ask me why. Here is a relevant portion of the log for the following installation:
[
...
2016/06/12 23:23:38 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.dash"
Rebuilding info directory
install-info: /usr/share/info/de.utf8: empty file
install-info: /usr/share/info/es.utf8: empty file
install-info: warning: no info dir entry in `/usr/share/info/maxima-index.lisp'
install-info: /usr/share/info/pt.utf8: empty file
install-info: /usr/share/info/pt_BR.utf8: empty file
install-info: warning: no info dir entry in `/usr/share/info/texdraw.info.gz'
2016/06/12 23:23:44 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_desktop-file-utils.sh"
2016/06/12 23:23:44 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_fontconfig_cache_1.sh"
/usr/share/texmf-dist/fonts/type1/public: failed to write cache
2016/06/12 23:23:54 abnormal exit: exit code=1
...
]
Executing this guy afterwards seems ok:
$ /etc/postinstall/zp_fontconfig_cache_1.sh
$ echo $?
0
--
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 reply other threads:[~2016-06-12 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 22:32 Mark McGregor [this message]
2016-06-12 23:15 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2016-06-12 23:36 Mark McGregor
2016-06-12 23:42 ` Ken Brown
2016-07-01 8:24 ` Václav Haisman
[not found] <1465768502.22005.ezmlm@cygwin.com>
2016-06-12 23:26 ` Mark McGregor
2016-06-12 23:35 ` Ken Brown
2016-06-12 21:32 Mark McGregor
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=trinity-f44febaf-a656-4566-b42a-bcccd2e6123a-1465767160468@3capp-gmx-bs72 \
--to=mark.mcgregor@gmx.de \
--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).