As the title states, quagga-0.99.4 fails to emerge as the MD5 checksum on the patches tarball fails to match up. Emerge output below: titan ~ # emerge -1v quagga Calculating dependencies... done! >>> Emerging (1 of 1) net-misc/quagga-0.99.4 to / >>> Downloading http://gentoo.osuosl.org/distfiles/quagga-0.99.4-patches-20060523.tar.gz --17:41:13-- http://gentoo.osuosl.org/distfiles/quagga-0.99.4-patches-20060523.tar.gz => `/nfs/distfiles/quagga-0.99.4-patches-20060523.tar.gz' Resolving gentoo.osuosl.org... 64.50.236.52, 64.50.238.52 Connecting to gentoo.osuosl.org|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 17,529 (17K) [application/x-gzip] 100%[====================================>] 17,529 110.11K/s 17:41:13 (109.97 KB/s) - `/nfs/distfiles/quagga-0.99.4-patches-20060523.tar.gz' saved [17529/17529] >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking quagga-0.99.4.tar.gz ;-) >>> checking quagga-0.99.4-patches-20060523.tar.gz !!! Digest verification failed: !!! /nfs/distfiles/quagga-0.99.4-patches-20060523.tar.gz !!! Reason: Failed on MD5 verification !!! Got: 06898616f1fabbb609c97b2e405d2460 !!! Expected: d28e0fa45ae762f4b5317eb13cc9a0c2 Seems to be a mirror agnostic problem and you'll notice the mirror I'm fetching from above is the master mirror from which files put on dev.g.o first appear (at least for the US).
oopsie... Byte 5 is different so I guess I've recreated the tarball before commiting the ebuild to the tree. I've uploaded the correct tarball into distfiles-local.
I've verified manifests using patch tarball downloaded from mirrors. Sorry for the trouble.
