Bug 220101 - description still contains "Mozilla" string
Summary: description still contains "Mozilla" string
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: seamonkey
Version: 3.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-18 22:06 UTC by Ben Levenson
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 18:39:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed patch (1.70 KB, patch)
2007-01-18 13:46 UTC, Martin Stransky
no flags Details | Diff

Description Ben Levenson 2006-12-18 22:06:33 UTC
+++ This bug was initially created as a clone of Bug #220098 +++

Description of problem:
description still contains "Mozilla" string:

Version-Release number of selected component (if applicable):
1.0.6-0.1.el4

Steps to Reproduce:
$ rpm -qp --qf "%{description}\n" seamonkey-1.0.6-0.1.el4.i386.rpm
Mozilla is an open-source web browser, designed for standards
compliance, performance and portability.

Comment 1 Ben Levenson 2006-12-18 22:07:21 UTC
er, the version-release for rhel-3 is 1.0.6-0.1.el3, not 1.0.6-0.1.el4

Comment 2 Martin Stransky 2007-01-18 13:46:36 UTC
Created attachment 145917 [details]
proposed patch

Comment 3 RHEL Program Management 2007-10-19 18:39:36 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.


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