Bug 154067 - postinstall script incorrectly runs mkfontdir
postinstall script incorrectly runs mkfontdir
Product: Fedora
Classification: Fedora
Component: urw-fonts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-04-06 19:30 EDT by Gerald Britton
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: F7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-15 09:37:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gerald Britton 2005-04-06 19:30:40 EDT
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):

How reproducible:

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

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
<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 Ngo Than 2007-06-15 09:37:47 EDT
it's fixed in FC6 and newest.

Note You need to log in before you can comment on or make changes to this bug.