From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin/X installation: Unable to extract /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20
Date: Mon, 12 Oct 2015 23:49:00 -0000 [thread overview]
Message-ID: <1444693763.3808.27.camel@cygwin.com> (raw)
In-Reply-To: <561465AE.1080700@cornell.edu>
On Tue, 2015-10-06 at 20:22 -0400, Ken Brown wrote:
> On 10/6/2015 7:40 PM, Michael Enright wrote:
> > Good old setup_x86 fortuitously gave me the chance to see an error
> > message involving one of these symlinks. I reviewed the setup log and
> > read that apparently such a symlink was created as follows:
> > io_stream:mklink
> > (cygfile:///etc/X11/fontpath.d/xorg-x11-75dpi:unscaled:pri=20 ->
> > cygfile:///usr/share/X11/fonts/75dpi)
> > But there is no /etc/X11/fontpath.d directory on the system.
> >
> > The man page doesn't say in explicit procedural terms what the end
> > user has to do to make fontpath.d exist and it doesn't seem to get
> > created by setup.
>
> That's because of the setup bug that I mentioned in
> https://www.cygwin.com/ml/cygwin/2015-10/msg00065.html; the directory
> will get created by setup once the fixed version of setup is released.
This should be fixed by setup 2.872, released today.
--
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
prev parent reply other threads:[~2015-10-12 23:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 14:42 kuaf
2015-10-06 15:05 ` Andrey Repin
2015-10-06 15:26 ` Ken Brown
2015-10-06 15:06 ` Ken Brown
2015-10-06 16:12 ` kuaf
2015-10-06 16:43 ` Michael Enright
2015-10-06 16:55 ` Ken Brown
2015-10-06 18:10 ` Jon Turney
2015-10-06 23:40 ` Michael Enright
2015-10-07 0:05 ` Andrey Repin
2015-10-07 0:22 ` Ken Brown
2015-10-12 23:49 ` Yaakov Selkowitz [this message]
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=1444693763.3808.27.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--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).