Bug 500606 - java-1.4.2-gcj-compat-debuginfo is epmty
Summary: java-1.4.2-gcj-compat-debuginfo is epmty
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: java-1.4.2-gcj-compat
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Rodney Russ
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-13 12:39 UTC by Alexander Todorov
Modified: 2014-09-01 11:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:01:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alexander Todorov 2009-05-13 12:39:32 UTC 
Description of problem:
java-1.4.2-gcj-compat-debuginfo is empty. IMHO it should never exist because java-1.4.2-gcj-compat package seems to contains symlinks and text files only.

Version-Release number of selected component (if applicable):
java-1.4.2-gcj-compat-debuginfo-1.4.2.0-40jpp.115.i386.rpm

How reproducible:
always

Steps to Reproduce:
1. rpm -qpl java-1.4.2-gcj-compat-debuginfo-1.4.2.0-40jpp.115.i386.rpm
2.
3.
  
Actual results:
empty package

Expected results:
no package is present

Additional info:
Comment 5 RHEL Program Management 2014-03-07 12:38:05 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 6 RHEL Program Management 2014-06-02 13:01:27 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).
Note You need to log in before you can comment on or make changes to this bug.