Bug 59619 - encodings.dir files disappear after upgrade to XFree86-4.2.0-6.30?
Summary: encodings.dir files disappear after upgrade to XFree86-4.2.0-6.30?
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: XFree86
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks: 61901
TreeView+ depends on / blocked
 
Reported: 2002-02-11 12:54 UTC by Jonathan Kamens
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-28 09:03:41 UTC
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2002-02-11 12:54:59 UTC
jik:~!73> rpm --verify XFree86-base-fonts
missing    /usr/X11R6/lib/X11/fonts/Speedo/encodings.dir
missing    /usr/X11R6/lib/X11/fonts/Type1/encodings.dir
missing    /usr/X11R6/lib/X11/fonts/misc/encodings.dir

What's up with that?

Comment 1 Mike A. Harris 2002-02-11 13:01:18 UTC
Not sure, but I'll look into it.  One thing to note, is that XFree86
no longer requires these files to be present, and XFree86.org has
deprecated them.  If I understand correctly, 4.3.0 when released will
have made the deprecation official, and by default the files will not
be produced, and 4.4.0 will not support it any longer.

I think what the problem is here, is missing %verify flags on that
subpackage for those files.  They also should be %ghost IMHO.



Comment 2 Mike A. Harris 2002-03-28 13:05:22 UTC
I have now added entries in the spec file to flag these files as ghosts,
so their existance will be owned, and they will bypass verification as
they are transient.

Again, note that encodings.dir files are deprecated by XFree86.org, and
are currently completely unnecessary.  XFree86 4.3.0 will not generate
or use encodings.dir any longer aparently, so these files will not be
supported in future releases.

The new flagged files are in build 4.2.0-6.51 and later in rawhide.

Thanks.


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