Bug 148787

Summary:	up2date does not upgrade fontconfig on multilib system
Product:	Red Hat Enterprise Linux 3	Reporter:	Eric Sandeen <sandeen>
Component:	fontconfig	Assignee:	Owen Taylor <otaylor>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	gbeshers, jh, martinez
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-06-13 16:06:31 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 Eric Sandeen 2005-02-15 16:49:58 UTC

Description of problem:

up2date doesn't want to upgrade fontconfig, because it thinks local
config file has changed:

The following Packages were marked to be skipped by your configuration:

Name                                    Version        Rel  Reason
-------------------------------------------------------------------------------
kernel                                  2.4.21         27.0.2.ELPkg
name/patternkernel-source                           2.4.21         27.0.2.ELPkg
name/patternfontconfig                              2.2.1          13   Config
modified
fontconfig                              2.2.1          13   Config modified


Version-Release number of selected component (if applicable):


[root@penguin12 root]# rpm -q fontconfig
fontconfig-2.2.1-6.0
fontconfig-2.2.1-6.0


How reproducible:

Every time I assume

Steps to Reproduce:
1. install RHEL3 on opteron w/ multilib support (not U*, just original RHEL3)
2.  run up2date
3.
  
Actual results:


Expected results:


Additional info:

guessing maybe this is the different md5 on:

/usr/bin/fc-cache etc?

--force takes care of the up2date problem :)

Comment 1 John Hesterberg 2007-02-15 16:40:09 UTC

Eric, you opened this while at SGI...
Do you think this is still an issue RH needs to address?
If not, close?

Comment 2 Eric Sandeen 2007-06-13 16:06:31 UTC

2 years later, appears nobody cares.  Closing.  No idea if it's still an issue
or not.