Bug 158215

Summary:	rpmrc and ppc64pseries and ppc64iseries macros files are broken
Product:	Red Hat Enterprise Linux 3	Reporter:	David Lehman <dlehman>
Component:	rpm	Assignee:	Panu Matilainen <pmatilai>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0
Target Milestone:	---
Target Release:	---
Hardware:	powerpc
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 19:01:58 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:
Bug Blocks:	190430

Description David Lehman 2005-05-19 17:14:34 UTC

Description of problem:
anaconda writes the canonical arch into /etc/rpm/platform. rpm uses this arch by
default when doing package builds. The problem is that the macros files for the
canonical arches are wrong. They don't define %_multilibno and %optflags is wrong.

More importantly, rpmrc doesn't have the correct buildarchtranslate entries for
ppc64pseries and ppc64iseries. 

Version-Release number of selected component (if applicable):
rpm-4.2.3-21_nonptl

How reproducible:
Always

Steps to Reproduce:
1. try to rebuild any package on a pSeries without using --target
2.
3.
  
Actual results:
The resulting package will be .ppc64pseries.rpm

Expected results:
The resulting package should be .ppc.rpm

Additional info:

Comment 5 RHEL Program Management 2007-10-19 19:01:58 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.