grace broken installation

Hans-Bernhard Bröker
Mon Jan 27 23:24:00 GMT 2020

Am 27.01.2020 um 13:58 schrieb Ken Brown:
> On 1/26/2020 10:25 PM, Hans-Bernhard Bröker wrote:
>> Am 25.01.2020 um 15:23 schrieb Rodrigo Medina:
>>> Hi,
>>> Both   installations of grace-5.1.24 and grace-5.1.245 are  broken.
>>> /usr/bin/xmgrace.exe runs but gives the message:
>>> --> Broken or incomplete installation - read the FAQ!
>>> and then quits.

>> After reading the FAQ and comparing with a direct build from upstream sources, I
>> find the reason for that is that the FontDataBase file of the distributed
>> package is, indeed, wrong.

>> Apparently the type1 font directory supplied by grace was replaced by a link to
>> ghostscript's type1 font repository.  But the FontDataBase wasn't updated to
>> match this change.  This mismatch causes xmgrace to baulk.  This change was made
>> between revisions 5.1.24 and 5.1.25 of the cygwin package, which neatly explains
>> why 5.1.24 works, but 5.1.25 does not.
> See

Yes, that's about what I figured.  The fonts supplied by xmgrace were 
replaced (in the cygport file) by a link to ghostscript's fonts, but 
then those were replaced by URW fonts, which broke xmgrace.

OTOH the particular font files xmgrace is looking for are in yet another 
place on Cygwin:


And indeed, making the /usr/share/grace/fonts/type1 symlink point there
does appear to fix the breakage.

So the minimal patch to grace.cygport (other than just leaving the type1 
directory of xmgrace alone) would be:

$ diff -uwp grace.cygport{~,}
--- grace.cygport~      2017-06-27 09:43:32.000000000 +0200
+++ grace.cygport       2020-01-28 00:08:56.345429500 +0100
@@ -78,7 +78,7 @@ src_install() {
         rmdir doc
         ln -sf ../doc/${NAME} doc
         rm -fr fonts/type1
-       ln -sf /usr/share/ghostscript/fonts fonts/type1
+       ln -sf /usr/share/X11/fonts/urw-fonts fonts/type1

         make_desktop_entry xmgrace Grace xmgrace 

An additional/changed dependency on the urw-base35-fonts-legacy package 
would probably be needed, but I'll have to leave that to people who 
understand Cygwin packaging.

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list