Bug 154067

Summary: postinstall script incorrectly runs mkfontdir
Product: [Fedora] Fedora Reporter: Gerald Britton <gbritton>
Component: urw-fontsAssignee: Than Ngo <than>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: F7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-15 13:37:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gerald Britton 2005-04-06 23:30:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
urw-fonts's postinstall scriptlet runs mkfontdir supplying non-existant
encodings directories resulting in fonts.dir failing to be created.

Version-Release number of selected component (if applicable):
urw-fonts-2.3-1

How reproducible:
Always

Steps to Reproduce:
1. yum install urw-fonts (prior to any X install)
2.
3.
  

Actual Results:  no fonts.dir created

Expected Results:  fonts.dir created properly

Additional info:

Commentary from mharris on the correct solution to this issue from IRC:

<mharris> xfs initscript runs mkfontdir in the same dirs always anyway, which
          invalidates mkfontdir being called with any args from any %post
          script
<mharris> I've told our font packagers 1000 times do not pass args to ttmkfdir
          or mkfontdir, as they will get blown away anyway, the first time xfs
          starts up
<mharris> Well, not necessarily the first time, but some time later perhaps,
          giving users different results
<mharris> All font packages should run mkfontdir/ttmkfdir/mkfontscale *only*
          the same way the xorg-x11.spec file does, and xfs.init
<mharris> Anything else will be overwritten.
<mharris> The only exception, is fonts.scale files in Type1 font directories.
<mharris> Because we do not ship type1inst
<mharris> At some point I plan on testing mkfontscale with all type1 fonts we
          ship and comparing the results it generates with the supplied
          fonts.scale files.
<mharris> If the results are identical, or it can be proven the static
          fonts.scale files are wrong in some way, I'll be calling mkfontscale
          on Type1 fonts always too.
<mharris> The reason for this, is 100% consistency.
<mharris> If args are needed absolutely for some certain font, then either the
          font is buggy, or the defaults in the tools aren't quite perfect and
          should be changed.

<mharris> You can paste what I said into the bug report too if you like.

Comment 1 Than Ngo 2007-06-15 13:37:47 UTC
it's fixed in FC6 and newest.