From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Fonts reorganization and additions
Date: Fri, 11 Sep 2015 16:29:00 -0000 [thread overview]
Message-ID: <55F30150.8020906@cornell.edu> (raw)
In-Reply-To: <55F2B932.8060101@gmail.com>
On 9/11/2015 7:21 AM, Ola Strömfors wrote:
> The update gave the following error:
>
> Unable to extract
> /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20
>
> The File is in use or some other error occurred.
>
> Please stop all Cygwin processes and select "Retry", or select
> "Continue" to go on anyway (the file will be updated after a reboot).
>
> and a similar message about the misc fonts.
>
> - Reboot did not help
> - After uninstalling the packages, creating the directory
> /etc/X11/fontpath.d and installing them again,
This looks like a packaging error. Yaakov, shouldn't installing
xorg-x11-fonts-* create /etc/X11/fontpath.d if it doesn't exist? From
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=etc%2FX11%2Ffontpath.d&arch=x86_64
it appears that terminus-fonts is the only package that creates this
directory.
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:[~2015-09-11 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441962346.9784.34.camel@cygwin.com>
2015-09-11 11:21 ` Ola Strömfors
2015-09-11 16:29 ` Ken Brown [this message]
2015-09-11 16:39 ` Yaakov Selkowitz
2015-09-11 17:50 ` Nem W Schlecht
2015-09-11 19:12 ` Ken Brown
2015-09-11 19:59 ` Yaakov Selkowitz
2015-09-11 21:36 ` Ken Brown
2015-09-12 15:36 ` Jim Reisert AD1C
2015-09-13 16:10 ` Ken Brown
2015-09-14 17:40 ` Ken Brown
2015-09-14 20:55 ` Ken Brown
2015-09-12 16:33 Fergus
2015-09-12 21:59 ` Ken Brown
2015-09-13 7:02 ` Fergus
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=55F30150.8020906@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).