From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: texlive-collection-*-20120312-1
Date: Wed, 14 Mar 2012 12:16:00 -0000 [thread overview]
Message-ID: <4F608BFE.5030107@cornell.edu> (raw)
In-Reply-To: <4F604C81.6040702@bonhard.uklinux.net>
On 3/14/2012 3:45 AM, Fergus wrote:
>>> This release is an update to the latest upstream packages.
>>> It also fixes some problems with the postinstall scripts.
>
>
> Thank you for all this work. Really amazing provision. FYI after this
> update I got the following error messages. From memory, there were no
> error messages at all after the first installation of texlive-collection
> and postinstall. The file /var/log/setup.log.full is very extensive (I
> doubt anybody wants it so haven't attached it) with many entries of the
> following style and all reporting exit code 146.
>
> /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?
Ken
--
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:[~2012-03-14 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 7:45 Fergus
2012-03-14 12:16 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-14 16:31 Fergus
2012-03-14 16:59 ` Ken Brown
2012-03-14 17:20 ` Andrey Repin
2012-03-14 15:59 Fergus
2012-03-14 16:02 ` Ken Brown
2012-03-13 19:56 Ken Brown
2012-03-14 13:53 ` Fergus
2012-03-14 14:33 ` Ken Brown
2012-03-28 10:47 ` JohnPeterson
2012-03-28 13:10 ` Ken Brown
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=4F608BFE.5030107@cornell.edu \
--to=kbrown@cornell.edu \
--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).