Bug 474060 - mash mishandles exclusivearch on noarch packages
Summary: mash mishandles exclusivearch on noarch packages
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mash
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F11Blocker, F11FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2008-12-01 22:26 UTC by Jesse Keating
Modified: 2014-03-17 03:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-14 00:42:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Patch for issue (1.38 KB, patch)
2008-12-02 01:06 UTC, Jesse Keating 		no flags Details | Diff
View All

Description Jesse Keating 2008-12-01 22:26:48 UTC 
When filtering out noarch packages based on ExcludeArch or ExclusiveArch, mash mishandles the ExclusiveArch case, because 'noarch' is one of the arches in ExclusiveArch in order for the package to build.  I'm looking at a way to patch this, but for now I wanted to get the bug filed.
Comment 1 Jesse Keating 2008-12-01 22:35:02 UTC 
Ah, right, case in point is the ipw2100-firmware and ipw2200-firmware packages.  They are noarch, and have ExclusiveArch i386 x86_64 ppc noarch or some such.  They are winding up in the ppc(64) directories when they shouldn't.
Comment 2 Jesse Keating 2008-12-02 01:06:35 UTC 
Created attachment 325322 [details]
Patch for issue
Comment 3 Bill Nottingham 2008-12-02 03:53:45 UTC 
Added to git. Is this causing significant compose issues that require a respin now?
Comment 4 Jesse Keating 2008-12-02 05:34:03 UTC 
I don't believe so.  The only packages catching this now are the ipw2?00-firmware packages.  appliance-tools was triggering it, and led to my initial investigation, but that one is being fixed with ExcludeArch vs ExclusiveArch.
Comment 5 Jesse Keating 2009-04-14 00:42:56 UTC 
I do believe this has been built for rawhide.
Note You need to log in before you can comment on or make changes to this bug.