Bug 1055622
| Summary: | boost-devel i686 and x86_64 bit packages on RHEL-6 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | boost | Assignee: | Petr Machata <pmachata> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.5 | CC: | alanm, jhunt, jkurik, jsvarova, lkocman, mcermak, mfranc, mnewsome, pmachata, pm-eus, riehecky |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Due to the way the Python programming language was packaged for Red Hat Enterprise Linux, the boost packages could not be shipped to secondary architectures. For example, boost-devel.i686 was not available on the x86-64 architecture. The Python packaging has been updated, and it is now possible to install secondary-architecture versions of the boost packages.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-03-25 10:16:12 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: | |||
| Bug Depends On: | 1037680 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2014-01-20 15:57:15 UTC
*** Bug 1055621 has been marked as a duplicate of this bug. *** Ok, I'm on it. Can I get agreement on definitive list of rpms we've agreed on being multilib? > 319 '^boost-devel$',\ > 320 '^boost-mpich2-devel$',\ > 321 '^boost-mpich2-python$',\ > 322 '^boost-openmpi-devel$',\ > 323 '^boost-openmpi-python$',\ > 324 '^boost-python$',\ These ^ were suggested and tested in original Bug 1037680 I'd like to do some cleanup, since these all were filtered because of python. Lubos 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/RHEA-2014-0325.html |