Bug 179259 (FE-ExcludeArch-x64, F-ExcludeArch-x64)

Summary: ExcludeArch Tracker for x86_64
Product: [Fedora] Fedora Reporter: Nobody's working on this, feel free to take it <nobody>
Component: distributionAssignee: Nobody's working on this, feel free to take it <nobody>
Status: ASSIGNED --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dominik, extras-qa
Target Milestone: ---Keywords: Tracking
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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: 177248, 179674, 182512, 182514, 185085, 185511, 194441, 198764, 202893, 204166, 219096, 229384, 234281, 237423, 239467, 253142, 391531, 428539, 432212, 435074, 435508, 436656, 440945    
Bug Blocks:    

Description Thorsten Leemhuis (ignored mailbox) 2006-01-29 10:37:02 UTC 
From the package review guidelines:
---
MUST: If the package does not successfully compile, build or work on an
architecture, then those architectures should be listed in the spec in
ExcludeArch. Each architecture listed in ExcludeArch needs to have a bug filed
in bugzilla, describing the reason that the package does not compile/build/work
on that architecture. The bug number should then be placed in a comment, next to
the corresponding ExcludeArch line. New packages will not have bugzilla entries
during the review process, so they should put this description in the comment
until the package is approved, then file the bugzilla entry, and replace the
long explanation with the bug number.
---
This Bug is used as a tracker for such issues. If you added a bug for a package
that uses ExcludeArch mark is as blocking this bug. If it's unlikely that the
issue is ever fixed feel free to close the bug directy after reporting.
Otherwise leave it open.
Comment 2 Jon Stanley 2008-03-28 01:46:28 UTC 
Adding Tracking keyword
Comment 3 David Lawrence 2009-08-04 18:27:31 UTC 
Reporter changed to nobody by request of Thorsten Leemhuis.