emerge xfree failed because of bad md5 for the aforementioned file. I removed and repeated, then changed mirrors, and that mirror gave me a good file. Reproducible: Always Steps to Reproduce: 1.fetch file from gentoo.oregonstate.edu 2.md5sum fails 3.other mirrors give good file Actual Results: happiness Expected Results: gotten the right file from oregonstate.edu What's the diff? peabody tmp # diff -u XFree86-compose.dir ostate-XFree86-compose.dir --- XFree86-compose.dir 2003-04-08 16:37:50.000000000 -0700 +++ ostate-XFree86-compose.dir 2003-06-01 09:11:27.000000000 -0700 @@ -8,7 +8,7 @@ XCOMM XCOMM some special -C/Compose: C +iso8859-1/Compose: C en_US.UTF-8/Compose: UTF-8 iso8859-1/Compose: ISO-8859-1 iso8859-2/Compose: ISO-8859-2 peabody tmp #
I would say exactly the opposite... gentoo.oregonstate.edu when I checked DID have the good XFree86-compose... file, but gentoo.linux.no for example did not. (probably due to a latency of the mirroring) So I guess that for the initial poster of this bug ; an emerge rsync rather than the fetching of the file on another mirror would have done the trick...
This is now fixed on the OSU server and will propogate out from there.