Bug 833545
Summary: | dependencies on php-common are not arch-specific. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | M. Ellis <michael.ellis> |
Component: | php | Assignee: | Remi Collet <rcollet> |
Status: | CLOSED ERRATA | QA Contact: | David Kutálek <dkutalek> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.5 | CC: | rcollet |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 10:14:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
M. Ellis
2012-06-19 18:19:48 UTC
I'd guess your optional repo is not in synch. php-mbstring comes from optional. It depends on php-common with matching NVR though without an arch-specific requirement. yum is finding an old php-mbstring.x86_64, and an old php-common.i686 (-3.el6_2.6) which matches the NVR requirement, but that conflicts with the new php-common.x86_64 (-3.el6_2.8). The deps should be tight enough to show a conflict earlier, but you would get a conflict anyway since that old php-mbstring cannot be installed. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0514.html |