The recorded cksums in the prefix-tree for following files differ from those in the mainline-tree: (on a Solaris 10 server with prefix in my $HOME) -bash-3.2$ md5sum /tmp/rmsh-gentoo/distfiles/binutils-2.* | grep checksum ccd264a5fa9ed992a21427c69cba91d3 /tmp/rmsh-gentoo/distfiles/binutils-2.18.tar.bz2._checksum_failure_.v80LlM 023222f392e9546bcbb0b4c0960729be /tmp/rmsh-gentoo/distfiles/binutils-2.19.1.tar.bz2._checksum_failure_.drNeSz 2b9dc8f2b7dbd5ec5992c6e29de0b764 /tmp/rmsh-gentoo/distfiles/binutils-2.20.1.tar.bz2._checksum_failure_.B0Q0k8 and on a server running Gentoo/Linux: ~ # md5sum /usr/portage/distfiles/binutils-2.* 3f8ce2a3b8096bdba641b987455f4bb0 /usr/portage/distfiles/binutils-2.18-patches-1.9.tar.bz2 ccd264a5fa9ed992a21427c69cba91d3 /usr/portage/distfiles/binutils-2.18.tar.bz2 09a1bdbfff377e816c844c41b1dd4aa0 /usr/portage/distfiles/binutils-2.20.1-patches-1.1.tar.bz2 2b9dc8f2b7dbd5ec5992c6e29de0b764 /usr/portage/distfiles/binutils-2.20.1.tar.bz2 7babbede162cec5c1f5dd57a046cc336 /usr/portage/distfiles/binutils-2.21.1-patches-1.3.tar.bz2 bde820eac53fa3a8d8696667418557ad /usr/portage/distfiles/binutils-2.21.1.tar.bz2 as you can the renamed files on the Solaris-server have the same checksums as the distfiles on the Linux-server. The patch-tarballs are not affected.
I took the Manifest from gx86 as input, indeed caused some redownloads, so should be fixed now
