Comment 14 for bug 386307

Alvin:
The rationale for those packages is slightly different, since not fixing it will not result in a oversized server CD, which makes those a lot less critical.

In particular, the trick I've been mostly using (building the package for any architecture, rather than once for "all") is costly in terms of resources, so we wanted to limit it to a few key packages. However this question might be revisited for next release as we move to JIT capabilities on alternate archs, and then using "Suggests" will have no downside.

I'd suggest opening another bug to track the remaining ones (with one package task for each source package, using "Also affects distribution...")

Thanks !