Thanks, Archie. For a minute I thought I hadn't made myself clear enough.
But doesn't that mean converting to 64-bit and upgrading are two separate processes, and isn't upgrading as we go asking for trouble?
It seems to me that a script would be far better at working out dependencies to build packages in the right order, and then install them all, than human trial and error, and the rebuild could run largely unattended. Of course, some packages probably would fail because they're not right for the architecture or might not work as intended, but wouldn't it be better to concentrate the human effort on dealing with those?
So by submitting SRPMs rebuilt on our 64-bit systems we're achieving very little that couldn't be done better automatically using the existing SRPMs. If we think we're helping Texstar rebuild we're deluding ourselves.
$ md5sum Dropbox/SRPMS/lxautostart-0.6.5-1leiche2011.src.rpm
$ md5sum Dropbox/SRPMS/x86_64/lxautostart-0.6.5-1leiche2011.src.rpm
The social benefit might be nice, but it's not the object of the exercise.