Bug 446506 - pirut doesn't install the expected arch
pirut doesn't install the expected arch
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pirut (Show other bugs)
5.2
All Linux
medium Severity medium
: rc
: ---
Assigned To: James Antill
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-14 17:21 EDT by Ben Levenson
Modified: 2013-03-12 16:10 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-12 16:10:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ben Levenson 2008-05-14 17:21:19 EDT
Description of problem:
1- install x86_64 client
2- add workstation repo
3- launch pirut
4- add several Development-specific package groups
5- try to rebuild an x86_64 package after the pirut update completes
On x86_64 a couple of necessary *-devel.x86_64 packages are not installed, even
though pirut did install the 32-bit versions:
cairo-devel.x86_64
fontconfig-devel.x86_64

But it doesn't even attempt to install the x86_64 version.

Version-Release number of selected component (if applicable):
pirut-1.3.28-13.el5
yum-3.2.8-9.el5
Comment 1 Ben Levenson 2008-05-14 17:28:11 EDT
a few more 64-bit RPMS that were missed, but the 32-bit versions were pulled
into the original pirut RPM transaction:
libIDL-devel.x86_64
xorg-x11-proto-devel.x86_64
dbus-glib-devel.x86_64
Comment 2 James Antill 2013-03-12 16:10:15 EDT
This request was evaluated by Red Hat Engineering for inclusion in a Red 
Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat 
Enterprise Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in 
response to customer and partner requirements, Red Hat takes a 
conservative approach when evaluating enhancements for inclusion in 
maintenance updates for currently deployed products. The primary 
objectives of update releases are to enable new hardware platform 
support and to resolve critical defects.

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