Bug 154407

Summary: [PATCH] per package arch spec in kickstart %packages broken
Product: Red Hat Enterprise Linux 4 Reporter: David Lehman <dlehman>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED ERRATA QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2005-220 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-09 11:29:54 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:
Attachments:
Description Flags
Patch from Issue Tracker ticket none

Description David Lehman 2005-04-11 15:15:45 UTC 
Description of problem:
specifying architecture of a given package generates errors saying, eg: package
zlib.i386 does not exist.

Version-Release number of selected component (if applicable):
anaconda-10.1.1.13-1

How reproducible:
Always on multilib systems.

Steps to Reproduce:
1. Specify "Compatibility Arch Support" but not "Compatibility Arch Development
Support" comps in a kickstart config.
2. Explicitly specify a multilib devel package, eg: 'zlib-devel.i386' on x86_64
3. Run the kickstart
  
Actual results:
"You have specified that the "
"package 'zlib-devel.i386' should be installed.  "
"This package does not exist. "
"Would you like to continue or "
"abort your installation?"

Expected results:
Successful installation of i386 zlib-devel package.

Additional info:
Comment 1 David Lehman 2005-04-11 15:15:45 UTC 
Created attachment 112949 [details]
Patch from Issue Tracker ticket
Comment 2 Paul Nasrat 2005-04-11 15:28:31 UTC 
This is already commited (as of this morning) to the rhel4 branch of anaconda -
is this a candidate for U1 still or U2?
Comment 3 Tim Powers 2005-06-09 11:29:54 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 the 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-2005-220.html