Bug 2497 - When 8859-2 package is installed path is not added to xfs configuration!
When 8859-2 package is installed path is not added to xfs configuration!
Product: Red Hat Linux
Classification: Retired
Component: XFree86-ISO8859-2 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-05-03 04:09 EDT by alien
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-06-11 14:17:01 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 alien 1999-05-03 04:09:11 EDT
Installing 8859-2 package won't automatically add path to
new fonts in xfs configuration! (/etc/X11/xfs/), so fonts
are unavailable f not added by hand!
Comment 1 Milan Kerslager 1999-06-07 18:01:59 EDT
This is caused by installation proces. When fonts are installed no
xfs server is in system yet. The solution is use triggered
postinstall scripts. Triggerred version you can found there:
I tryed to use Prereq: in spec file but this didn't work. Triggers
are the best way to solve this problem.

------- Email Received From  Milan Kerslager <milan.kerslager@spsselib.hiedu.cz> 06/07/99 18:37 -------
Comment 2 Preston Brown 1999-06-11 14:17:59 EDT
The ISO 8859-2 fonts we ship prerequire chkfontpath, and chkfontpath
requires xfs, so if you have both of these packages on the system,
everything should happen automatically.

If you are experiencing problems with the path not being added at
_initial installation time_, this is a known bug in RPM (it doesn't
reorder the dependency list 100% correctly).  There is a fix on the
errata page for Red Hat 6.0 (i.e. manually run chkfontpath to add the

After this, installing packages that use chkfontpath to modify the
font path should work smoothly.

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