Bug 679121
| Summary: | php-pear with php53 produces many warnings | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Martin Poole <mpoole> |
| Component: | php-pear | Assignee: | Joe Orton <jorton> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.6 | CC: | anshockm, brsmith, cww, dbasant, ddumas, dkutalek, labradort, msvoboda, sergio.pasra, sixy, wnefal+redhatbugzilla, yury |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When PEAR was used with the php53 package, the "pear" command emitted numerous redundant deprecation warnings. These warnings have been disabled and the "pear" command now behaves as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-27 08:14:02 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
Martin Poole
2011-02-21 16:33:42 UTC
The upstream solution to this was not to clean up the pear code but simply to mask off all deprecation warnings. http://pear.php.net/bugs/bug.php?id=13323&edit=12&patch=Ignore.E_DEPRECATED.as.fast.solution&revision=latest This kludge was introduced in 1.7.2 and is still present in the RHEL6 version 1.9.0 and latest upstream 1.9.1 This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. *** Bug 673521 has been marked as a duplicate of this bug. *** *** Bug 664539 has been marked as a duplicate of this bug. *** Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. Sorry, I did not intend to close this bug. Bug https://bugzilla.redhat.com/show_bug.cgi?id=673521 673521 has the description "PHP53 Lacks php53-pear". Technically, a different issue. Should not have been merged. Please do not close or decline the request. Pear needs to be updated and not left behind! php-pear should conflict with php53. php53-pear should be provided instead. *** Bug 673521 has been marked as a duplicate of this bug. *** > Yury, there is no need for a separate pear package to work with 5.3, the
> existing php-pear will work once the warnings are fixed.
I am not quite sure if it makes sense to provide PEAR 1.4.9 which is god knows how old (the latest stable ATM is 1.9.4) for php53, since if an application *does* require php53, I believe it would also expect a reasonably recent matching PEAR version to be installed.
I feel that it is a much better idea to provide PEAR from RHEL6 (1.9.0 if I am not mistaken) for php53 renamed as php53-pear on RHEL5. This also means that you don't have to touch php-pear at all, which is surely a plus, but rather provide a new totally independent package which is also already maintained for RHEL6 and is not going to influence anything else.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When PEAR was used with the php53 package, the "pear" command emitted numerous redundant deprecation warnings. These warnings have been disabled and the "pear" command now behaves as expected.
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. http://rhn.redhat.com/errata/RHBA-2011-1097.html |