Re: Fonts reorganization and additions

Re: Fonts reorganization and additions

[Ola Strömfors]

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, there are still
   fonts missing, e.g.

% xterm
Warning: Cannot convert string 
"-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset

/Ola

> The following packages have been uploaded to the Cygwin distribution:
>
> * adobe-source-code-pro-fonts-1.017-2
> * adobe-source-sans-pro-fonts-1.050-2
> * adobe-source-serif-pro-fonts-1.017-1
> * alef-fonts-1.0-2
> * artwiz-aleczapka-fonts-1.3-2
> * cantarell-fonts-0.0.16-2
> * culmus-fonts-0.130-1
> * dejavu-fonts-2.35-1
> * gnu-free-fonts-20120503-2
> * inconsolata-fonts-1.010-1
> * kanjistrokeorders-fonts-3.001-1
> * liberation-fonts-1.07.4-1
> * linux-libertine-fonts-5.3.0-1
> * overpass-fonts-2.0-1
> * oxygen-fonts-5.3.2-2
> * sj-fonts-2.0.2-2
> * terminus-fonts-4.40-1
> * unifont-fonts-8.0.01-1
> * xorg-x11-fonts-cyrillic-7.5-1
> * xorg-x11-fonts-ethiopic-7.5-1
> * xorg-x11-fonts-dpi100-7.5-1
> * xorg-x11-fonts-dpi75-7.5-1
> * xorg-x11-fonts-misc-7.5-1
> * xorg-x11-fonts-Type1-7.5-1
>
> These packages have been renamed and reorganized for the new font layout
> used by xorg-server-1.17.2-4, xfs-1.1.4-1, and tigervnc-server-1.5.0-1.
> X11 core fonts are installed into /usr/share/X11/fonts with the
> necessary symlinks into the X11 font catalogue.  Other fonts are
> installed in their own directories under /usr/share/fonts, along with
> configuration files in the requisite locations, for use with fontconfig.
>
> --
> 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

Re: Fonts reorganization and additions

[Ken Brown]

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

Re: Fonts reorganization and additions

[Yaakov Selkowitz]

On Fri, 2015-09-11 at 12:29 -0400, Ken Brown wrote:
> 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.

They do already, and they show up in the search.

--
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

Re: Fonts reorganization and additions

[Nem W Schlecht]

I got these new font packages and although I saw the announcement, the
two mirrors I've tried do not have the updated xorg-server yet
(although they both have these updated font packages).  Is there a way
to make a sub-version (1.17.2-4 for xorg-server, not 1.17.2-3 as is
listed below, contains the font path changes) a requirement?  Would
have saved me a little bit of a headache this morning as well.

On Fri, Sep 11, 2015 at 11:40 AM, Yaakov Selkowitz
<yselkowitz@cygwin.com> wrote:
> On Fri, 2015-09-11 at 12:29 -0400, Ken Brown wrote:
>> 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.
>
> They do already, and they show up in the search.
>
> --
> 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
>



-- 
Nem W Schlecht                   nem@emptec.com
Empyreal Technologies    http://www.emptec.com/
 "Perl did the magic.  I just waved the wand."

--
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

Re: Fonts reorganization and additions

[Ken Brown]

On 9/11/2015 12:40 PM, Yaakov Selkowitz wrote:
> On Fri, 2015-09-11 at 12:29 -0400, Ken Brown wrote:
>> 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.
>
> They do already, and they show up in the search.

I was referring to the fact that for terminus-fonts we see

     2015-09-10 19:57           0 etc/
     [...]
     2015-09-10 19:57           0 etc/X11/
     2015-09-10 19:57           0 etc/X11/fontpath.d/
     2015-09-10 19:57           0 etc/X11/fontpath.d/terminus:unscaled -> 
/usr/share/fonts/terminus

whereas for xorg-x11-fonts-dpi75 we see only

     2015-09-10 20:44           0 
etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20 -> 
/usr/share/X11/fonts/75dpi

and similarly for the other xorg-x11-fonts-* packages.

I interpreted this as meaning that /etc/X11/fontpath.d wouldn't get created, but 
maybe I was wrong.

In any case, it apparently didn't get created for the OP, and I had the same 
experience.  On the other hand, it gets created when I manually unpack the 
tarball, so I don't know what's going on.

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

Re: Fonts reorganization and additions

[Yaakov Selkowitz]

On Fri, 2015-09-11 at 15:12 -0400, Ken Brown wrote:
> I was referring to the fact that for terminus-fonts we see

>      2015-09-10 19:57           0 etc/X11/
>      2015-09-10 19:57           0 etc/X11/fontpath.d/
>      2015-09-10 19:57           0 etc/X11/fontpath.d/terminus:unscaled -> /usr/share/fonts/terminus
> 
> whereas for xorg-x11-fonts-dpi75 we see only
> 
>      2015-09-10 20:44           0 etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20 -> /usr/share/X11/fonts/75dpi
> 
> and similarly for the other xorg-x11-fonts-* packages.
>  
> I interpreted this as meaning that /etc/X11/fontpath.d wouldn't get created, but 
> maybe I was wrong.

Generally, the leading directories aren't required, setup should be
creating all parent directories regardless.

> In any case, it apparently didn't get created for the OP, and I had the same 
> experience.  On the other hand, it gets created when I manually unpack the 
> tarball, so I don't know what's going on.

If you remove your /etc/X11/fontpath.d and just (re)install
xorg-x11-fonts-Type1, does this occur?  (It shouldn't.)

The first thing that should be checked is if the code in setup which
allows it to unpack files with "illegal" characters in Windows also
makes sure to create parent directories.  Based on these reports my
*guess* is it doesn't but I haven't looked yet.

--
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

Re: Fonts reorganization and additions

[Ken Brown]

On 9/11/2015 3:59 PM, Yaakov Selkowitz wrote:
> On Fri, 2015-09-11 at 15:12 -0400, Ken Brown wrote:
>> I was referring to the fact that for terminus-fonts we see
>
>>       2015-09-10 19:57           0 etc/X11/
>>       2015-09-10 19:57           0 etc/X11/fontpath.d/
>>       2015-09-10 19:57           0 etc/X11/fontpath.d/terminus:unscaled -> /usr/share/fonts/terminus
>>
>> whereas for xorg-x11-fonts-dpi75 we see only
>>
>>       2015-09-10 20:44           0 etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20 -> /usr/share/X11/fonts/75dpi
>>
>> and similarly for the other xorg-x11-fonts-* packages.
>>
>> I interpreted this as meaning that /etc/X11/fontpath.d wouldn't get created, but
>> maybe I was wrong.
>
> Generally, the leading directories aren't required, setup should be
> creating all parent directories regardless.
>
>> In any case, it apparently didn't get created for the OP, and I had the same
>> experience.  On the other hand, it gets created when I manually unpack the
>> tarball, so I don't know what's going on.
>
> If you remove your /etc/X11/fontpath.d and just (re)install
> xorg-x11-fonts-Type1, does this occur?  (It shouldn't.)

No, it doesn't.  So your guess below is probably correct.

> The first thing that should be checked is if the code in setup which
> allows it to unpack files with "illegal" characters in Windows also
> makes sure to create parent directories.  Based on these reports my
> *guess* is it doesn't but I haven't looked yet.

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

Re: Fonts reorganization and additions

[Jim Reisert AD1C]

I also had things installed "out of order".  The new Xorg server
package didn't arrive until after I had installed the updated font
packages.  Saturday morning, I was able to install the latest Xorg
server, but found I did not have an /etc/X11/fontpath.d directory, so
I re-installed my two font packages:

    xorg-x11-fonts-dpi75
    xorg-x11-fonts-misc

While I can startup Emacs again without -Q, the default Emacs font is
bigger than what I had before, using:

emacs.font:             -adobe-courier-medium-r-*-*-*-96-*-*-*-*-iso8859-1

How do I return to the smaller font specified above?

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
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

Re: Fonts reorganization and additions

[Ken Brown]

On 9/11/2015 3:59 PM, Yaakov Selkowitz wrote:
> The first thing that should be checked is if the code in setup which
> allows it to unpack files with "illegal" characters in Windows also
> makes sure to create parent directories.  Based on these reports my
> *guess* is it doesn't but I haven't looked yet.

I'm not very familiar with the setup code, but I think I may have found the 
problem.  The function mkdir_p() in mkdir.cc contains the following, starting at 
line 99:

   for (c = path; *c; c++)
     {
       if (*c == ':')
	slash = 0;
       if (*c == '/' || *c == '\\')
	slash = c;
     }

   if (!slash)
     return 0;

If I understand this correctly, the function will return success without having 
created the leading directory if the path name contains a colon and doesn't 
contain a slash after the last colon.  I guess the assumption is that there is 
no "leading directory" to be created in this case.  [This part of the code was 
written in 2000, when a colon could not be part of a file name.]

I hope someone who understands the setup code better than I do can take a look 
at this.  I'm not confident that I understand all the uses of mkdir_p() or all 
possible reasons why its in_path argument might contain a colon.

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

Re: Fonts reorganization and additions

[Ken Brown]

On 9/13/2015 12:10 PM, Ken Brown wrote:
> On 9/11/2015 3:59 PM, Yaakov Selkowitz wrote:
>> The first thing that should be checked is if the code in setup which
>> allows it to unpack files with "illegal" characters in Windows also
>> makes sure to create parent directories.  Based on these reports my
>> *guess* is it doesn't but I haven't looked yet.
>
> I'm not very familiar with the setup code, but I think I may have found
> the problem.  The function mkdir_p() in mkdir.cc contains the following,
> starting at line 99:
>
>    for (c = path; *c; c++)
>      {
>        if (*c == ':')
>      slash = 0;
>        if (*c == '/' || *c == '\\')
>      slash = c;
>      }
>
>    if (!slash)
>      return 0;
>
> If I understand this correctly, the function will return success without
> having created the leading directory if the path name contains a colon
> and doesn't contain a slash after the last colon.  I guess the
> assumption is that there is no "leading directory" to be created in this
> case.  [This part of the code was written in 2000, when a colon could
> not be part of a file name.]
>
> I hope someone who understands the setup code better than I do can take
> a look at this.  I'm not confident that I understand all the uses of
> mkdir_p() or all possible reasons why its in_path argument might contain
> a colon.

The following patch fixes the problem:

diff --git a/mkdir.cc b/mkdir.cc
index dabc256..84bb176 100644
--- a/mkdir.cc
+++ b/mkdir.cc
@@ -98,8 +98,6 @@ mkdir_p (int isadir, const char *in_path, mode_t mode)

    for (c = path; *c; c++)
      {
-      if (*c == ':')
-       slash = 0;
        if (*c == '/' || *c == '\\')
         slash = c;
      }

I don't know if this might cause some other problem, but it seems OK in 
limited testing.

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

Re: Fonts reorganization and additions

[Ken Brown]

On 9/14/2015 1:40 PM, Ken Brown wrote:
> On 9/13/2015 12:10 PM, Ken Brown wrote:
> The following patch fixes the problem:
>
> diff --git a/mkdir.cc b/mkdir.cc
> index dabc256..84bb176 100644
> --- a/mkdir.cc
> +++ b/mkdir.cc
> @@ -98,8 +98,6 @@ mkdir_p (int isadir, const char *in_path, mode_t mode)
>
>     for (c = path; *c; c++)
>       {
> -      if (*c == ':')
> -       slash = 0;
>         if (*c == '/' || *c == '\\')
>          slash = c;
>       }
>
> I don't know if this might cause some other problem, but it seems OK in
> limited testing.

If anyone else wants to test this, my builds are at

   http://sanibeltranquility.com/cygwin/setup-2.871-1-g0ef99d.tar.xz

This is based on the sources for setup 2.871, with the above patch applied.

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

RE: Fonts reorganization and additions

[Fergus]

>> ... are we awaiting a fix with a new timestamp?

>  I'm sure this will be fixed properly in due course. In the meantime,
here's a workaround:
1. Create the directory /etc/X11/fontpath.d.
2. Create a file in that directory. [This is to prevent deletion of the
directory during step 3.]
3. Reinstall xorg-x11-fonts-dpi75 and xorg-x11-fonts-misc.

Perfect. Fully functional again. Thank you.
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

Re: Fonts reorganization and additions

[Ken Brown]

On 9/12/2015 12:33 PM, Fergus wrote:
>>> I re-installed my two font packages:
>>>     xorg-x11-fonts-dpi75
>>>     xorg-x11-fonts-misc
>
> OK, sorry, I've tried every which way to recover from the consequences of
> this reorganisation including the re-installation described above by Jim
> Reisert using setup.ini timestamped 1442007529; but still got the "Error
> writing file" message
>>>    Unable to extract
>>>    /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20
> followed by
>>>    Unable to extract
>>>    /etc/X11/fontpath.d/xorg-x11-fonts-misc:unscaled:pri=10
> During the re-installation; and then the same message as before
>>> Warning: Cannot convert string
> "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct
> when starting xterm.
> Are users meant to be able to recover their glitch-free system using
> self-help (in which case can anybody please provide a recipe e.g. a
> sequenced re-installation?!) or are we awaiting a fix with a new timestamp?
> Just a question, not a nag ... thank you.

I'm sure this will be fixed properly in due course.  In the meantime, here's a 
workaround:

1. Create the directory /etc/X11/fontpath.d .

2. Create a file in that directory.  [This is to prevent deletion of the 
directory during step 3.]

3. Reinstall xorg-x11-fonts-dpi75 and xorg-x11-fonts-misc.

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

Re: Fonts reorganization and additions

[Fergus]

>> I re-installed my two font packages:
>>    xorg-x11-fonts-dpi75
>>    xorg-x11-fonts-misc

OK, sorry, I've tried every which way to recover from the consequences of
this reorganisation including the re-installation described above by Jim
Reisert using setup.ini timestamped 1442007529; but still got the "Error
writing file" message 
>>   Unable to extract
>>   /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20
followed by
>>   Unable to extract
>>   /etc/X11/fontpath.d/xorg-x11-fonts-misc:unscaled:pri=10
During the re-installation; and then the same message as before
>> Warning: Cannot convert string
"-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct
when starting xterm.
Are users meant to be able to recover their glitch-free system using
self-help (in which case can anybody please provide a recipe e.g. a
sequenced re-installation?!) or are we awaiting a fix with a new timestamp?
Just a question, not a nag ... thank you.
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