ebuild for bitkeeper 3.2.3 apparently has incorrect MD5 digest value for bk-3.2.3-x86-glibc23-linux.bin - 083742d2867941c92a8945b178db281f. The file however has the digest fcf34e57a1e7e83606e6f5c6067dcf4b , and this corresponds to the bitkeeper.com : fcf34e57a1e7e83606e6f5c6067dcf4b. see http://www.bitmover.com/download/bk-3.2.3/MD5SUMS Reproducible: Always Steps to Reproduce: 1.emrge bitkeeper 2. 3. Actual Results: sudo emerge bitkeeper Calculating dependencies ...done! >>> emerge (1 of 1) dev-util/bitkeeper-3.2.3 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 083742d2867941c92a8945b178db281f >>> your file's digest: fcf34e57a1e7e83606e6f5c6067dcf4b !!! File does not exist: /usr/portage/distfiles//bk-3.2.3-x86-glibc23-linux.bin Expected Results: should emerge bitkeeper
It seems it's not only the x86 file that has changed.. They've updated them all. Anyway, I've just submitted the changes to CVS. Thanks for reporting this.