Bug 278311

Summary: Wrong Provides for xpdf
Product: Red Hat Enterprise Linux 5 Reporter: Klaus Ethgen <Klaus+rhbz>
Component: popplerAssignee: Denise Dumas <ddumas>
Status: CLOSED WONTFIX QA Contact: desktop-bugs <desktop-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 5.0CC: Klaus+rhbz
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-02 13:01:30 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 Klaus Ethgen 2007-09-05 12:46:31 UTC
Description of problem:
As redhat seems to forget xpdf in the distribution we have readd them for our 
local distribution.

Unfortunate doing a "yum install xpdf" will ignore xpdf and install poppler-
utils. Apart from the not so political correct name "poppler" there is no xpdf 
binary inside poppler-utils. So poppler-utils do NOT have the functionality of 
xpdf.

How reproducible:
yum install xpdf

Actual results:
...
Installing:
 poppler-utils           i386       0.5.4-4.1.el5    rhel-i386-client-5   70 k
...

Expected results:
...
Installing:
 xpdf ...

Additional info:
At the moment there is the only solution to put a "exclude=poppler-utils" to 
yum.conf.

Comment 4 RHEL Program Management 2014-03-07 12:38:19 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 5 RHEL Program Management 2014-06-02 13:01:30 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).

Comment 6 Klaus Ethgen 2015-10-05 11:53:40 UTC
Well, if you just need 7 years to answer a bug report, that is your problem.