Red Hat Bugzilla – Full Text Bug Listing
|Summary:||ExcludeArch Tracker for i386|
|Product:||[Fedora] Fedora||Reporter:||Nobody's working on this, feel free to take it <nobody>|
|Component:||distribution||Assignee:||Nobody's working on this, feel free to take it <nobody>|
|Status:||ASSIGNED ---||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||dcantrell, dominik, extras-qa, luto|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||1040486, 1208441, 1340634, 1375732, 1440282, 1460582, 1474772, 1475223, 253142, 902875, 1210991, 1225215, 1474773|
Description Thorsten Leemhuis (ignored mailbox) 2006-01-29 05:35:38 EST
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-27 21:46:04 EDT
Adding Tracking keyword
Comment 3 David Lawrence 2009-08-04 14:27:18 EDT
Reporter changed to firstname.lastname@example.org by request of Thorsten Leemhuis.
Comment 4 Andy Lutomirski 2017-07-13 12:04:12 EDT
The upstream team is actively working on this. I think the relevant kernel patches are already upstream.
Comment 5 Andy Lutomirski 2017-07-13 12:05:53 EDT
Er, slight correction. Upstream is working on i386 checkpoint/restore on x86_64 kernels, so the package will be buildable soon. It won't *work* on a real i686 system, but that's a different story.