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.
Adding Tracking keyword
Reporter changed to email@example.com by request of Thorsten Leemhuis.
The upstream team is actively working on this. I think the relevant kernel patches are already upstream.
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.