If a TU is unable to build for x86_64 for whatever reason, I don't think it should be a problem if any other TU who has access to an x86_64 machine helps out with the difflist. Architecture specific changes are just a " $CARCH = x86_64 " away, and this won't compromise the i686 build in anyway. When I build for community64, I usually don't contact the TU maintaing the i686 package unless there's some major change required in the package to build for both arches. I'm however uncomfortable building certain packages for community, especially since I don't know how to test them...this especially applies to community/lib and commuinty/devel. And when the difflist is huge, I tend to rush thru the building/testing process, and thats something which I don't like doing(like today, where I think I did ~30 packages). If more TU's could help out with this, the difflist would be smaller, and it really wouldn't matter if a handful of people don't have the time to build for x86_64.
<br><br>Varun<br><br><br>