From: Fergus <fergus@bonhard.uklinux.net>
To: Cygwin ML <cygwin@cygwin.com>
Cc: Fergus <fergus@bonhard.uklinux.net>
Subject: Re: [ANNOUNCEMENT] Updated: texlive-collection-*-20120312-1
Date: Wed, 14 Mar 2012 13:53:00 -0000 [thread overview]
Message-ID: <4F60A2A1.5080208@bonhard.uklinux.net> (raw)
>> /usr/share/texmf-dist/fonts/type1/urw/symbol: failed to write cache
>> /usr/share/texmf-dist/fonts/type1/urw/times: failed to write cache
>> /usr/share/texmf-dist/fonts/type1/urw/zapfchan: failed to write cache
>> /usr/share/texmf-dist/fonts/type1/urw/zapfding: failed to write cache
>> 2012/03/14 07:29:42 abnormal exit: exit code=146
> Those errors are coming from the calls to fc-cache in the new
postinstall scripts.
> Do you have the latest version of fontconfig installed?
Thank you for getting back so rapidly.
Yes, fontconfig is installed (and therefore I assume latest version).
There is a
03/02/2012 09:11 178,702 /bin/cygfontconfig-1.dll
file There is also a /etc/postinstall/fontconfig.sh.done file.
(a) Incidentally I originally installed texlive-collection over an
obsolete tetex, which installation (a) took forever and (b) tailed off
at the end with a fontconfig installation error that I reported at
http://cygwin.com/ml/cygwin/2012-03/msg00226.html.
(b) So I then did what always seems to me to be the strategy of last
resort: re-install brand new Cygwin from the ground up. Evidently
successful - no error messages; presence of fontconfig.sh.done as
stated; and until today's update of texlive-collection-*-20120312-1, no
problems!
(c) Just this minute I tried setup.exe again. Nothing new to install
in the last 8 hours but setup still took 10 (no: nearer 20) minutes
labouring over postinstall scripts (presumably taking a second crack at
those it failed with previously? ... lacking the *.sh.done files?) and
ended with a *similar but different* error announcement
Previously (8 hours ago):
Package: texlive-collection-basic
texlive-collection-basic.sh exit code 146
Package: texlive-collection-fontsrecommended
texlive-collection-fontsrecommended.sh exit code 146
Package: texlive-collection-fontsextra
texlive-collection-fontsextra.sh exit code 146
Package: texlive-collection-pictures
texlive-collection-pictures.sh exit code 146
Package: texlive-collection-latexextra
texlive-collection-latexextra.sh exit code 146
Package: texlive-collection-science
texlive-collection-science.sh exit code 146
Now:
Package: Unknown package
texlive-collection-basic.sh exit code 146
texlive-collection-fontsextra.sh exit code 146
texlive-collection-fontsrecommended.sh exit code 146
texlive-collection-latexextra.sh exit code 146
texlive-collection-pictures.sh exit code 146
texlive-collection-science.sh exit code 146
Fergus
--
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 reply other threads:[~2012-03-14 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 19:56 Ken Brown
2012-03-14 13:53 ` Fergus [this message]
2012-03-14 14:33 ` Ken Brown
2012-03-28 10:47 ` JohnPeterson
2012-03-28 13:10 ` Ken Brown
2012-03-14 7:45 Fergus
2012-03-14 12:16 ` Ken Brown
2012-03-14 15:59 Fergus
2012-03-14 16:02 ` Ken Brown
2012-03-14 16:31 Fergus
2012-03-14 16:59 ` Ken Brown
2012-03-14 17:20 ` Andrey Repin
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=4F60A2A1.5080208@bonhard.uklinux.net \
--to=fergus@bonhard.uklinux.net \
--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).