Bug 441356 - RHEL4: Need newer perl-HTML-Parser for spamassassin
Summary: RHEL4: Need newer perl-HTML-Parser for spamassassin
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: perl-HTML-Parser
Version: 4.7
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Stepan Kasal
QA Contact: desktop-bugs@redhat.com
Depends On:
Blocks: 311151
TreeView+ depends on / blocked
Reported: 2008-04-07 18:20 UTC by Warren Togami
Modified: 2008-07-24 19:58 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2008-07-24 19:58:10 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0729 normal SHIPPED_LIVE perl-HTML-Parser bug fix update 2008-07-23 16:41:50 UTC

Description Warren Togami 2008-04-07 18:20:04 UTC
Bug #311151 spamassassin upgrade for RHEL4 requires a newer version of
perl-HTML-Parser than what RHEL4 provides.  If we do not do this, then we cannot
upgrade spamassassin on RHEL4.

Upgrade RHEL4 to match RHEL5's

We might name RHEL4's version:

Tim Burke says this needs both QA approval and for the perl owner to agree.

Comment 1 Stepan Kasal 2008-04-08 09:45:51 UTC
Reviewing file Changes, I noticed two sources of API incompatibility:
1) Since HTML-Parser-3.37 (2004-11-10), using HTML::Parser by creating a
subclass with modified method is no longer documented in the man page.  (It is
not clear if it still works or when it stopped working.)  But this interface was
used in HTML-Parser-2.x, which had its last release in 1999.
2) Since HTML-Parser-3.39_90 (2004-11-17), decoding Unicode entities is always
enabled.  This was a configure option previously and RHEL-4 had it disabled.
The upgrade from 3.35 to 3.55 presents four years of development: most
improvements happened in 2004, and only a few bug fixes in 2006 and 2007. I
conclude the new code has matured.

To sum up: I believe the function of this module is to parse current HTML, so
most of the customers will benefit from the many corrections introduced in the
development of the module.  The Unicode entities support also falls to the
category.  I believe these advantages overweight the slight risk of
incompatibility in the ancient corners of the API.

I recommend the upgrade of the module.

Comment 2 Warren Togami 2008-04-08 15:02:54 UTC
Assigned to you, does this mean you will be handling it?  I will need to wait
until it is built and in the buildroot before I am able to do Bug #311151.

Comment 13 errata-xmlrpc 2008-07-24 19:58:10 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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