The author(?) of thttpd and mini_httpd has apparently rebuilt the tarballs upstream to take in to account some recent email address changes, therefore the mirror files and digest files don't match upstream. Strangely confusing error messages abound when all your GENTOO_MIRRORS fail to resolve and you end up hitting the upstream server for a tarball like I did yesterday. To be truthful I only noticed the thttpd issue, but a quick grep of the portage tree for the domain turned up mini_httpd and the same problem. I believe they are the only two packages in the tree affected by the cosmetic changes to the tarballs happening on that server, but that is just the grep talking. Reproducible: Always Steps to Reproduce: 1. 2. 3.
>>> Emerging (1 of 1) www-servers/thttpd-2.25b-r4 to / >>> Downloading ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo/distfiles/thttpd-2.25b.tar.gz --14:02:54-- ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo/distfiles/thttpd-2.25b.tar.gz => `/usr/portage/distfiles/thttpd-2.25b.tar.gz' Resolving ftp.sh.cvut.cz... 147.32.127.222 Connecting to ftp.sh.cvut.cz|147.32.127.222|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /MIRRORS/gentoo/gentoo/distfiles ... done. ==> PASV ... done. ==> RETR thttpd-2.25b.tar.gz ... done. Length: 132,363 (129K) (unauthoritative) 100%[====================================================================================================>] 132,363 216.54K/s 14:02:55 (216.02 KB/s) - `/usr/portage/distfiles/thttpd-2.25b.tar.gz' saved [132363] >>> thttpd-2.25b.tar.gz MD5 ;-) >>> thttpd-2.25b.tar.gz size ;-) >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking thttpd-2.25b.tar.gz ;-) --- >>> Emerging (1 of 1) www-servers/mini_httpd-1.19 to / >>> Downloading ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo/distfiles/mini_httpd-1.19.tar.gz --14:03:24-- ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo/distfiles/mini_httpd-1.19.tar.gz => `/usr/portage/distfiles/mini_httpd-1.19.tar.gz' Resolving ftp.sh.cvut.cz... 147.32.127.222 Connecting to ftp.sh.cvut.cz|147.32.127.222|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /MIRRORS/gentoo/gentoo/distfiles ... done. ==> PASV ... done. ==> RETR mini_httpd-1.19.tar.gz ... done. Length: 42,142 (41K) (unauthoritative) 100%[====================================================================================================>] 42,142 148.93K/s 14:03:25 (148.91 KB/s) - `/usr/portage/distfiles/mini_httpd-1.19.tar.gz' saved [42142] >>> mini_httpd-1.19.tar.gz MD5 ;-) >>> mini_httpd-1.19.tar.gz size ;-) >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking mini_httpd-1.19.tar.gz ;-)
Yeah, and that works for me too. However, that wasn't what the bug report was about. Here are the md5sums for upstream, and from the tree: 0 jay@shine ~/test $ md5sum * 7c68293ad265ecfe2edea917912f6f1f mini_httpd-1.19.tar.gz 156b249b3b0bcd48b06badd2db0d56c5 thttpd-2.25b.tar.gz www-servers/mini_httpd/files/digest-mini_httpd-1.19:MD5 792a529dfe974355aad8ba6c80e54e7a mini_httpd-1.19.tar.gz 42142 www-servers/thttpd/files/digest-thttpd-2.25b-r4:MD5 a0e9cd87455d3a0ea11e5ea7e947adf6 thttpd-2.25b.tar.gz 132363
So what? The digests are correct on the mirrors, messing with this will just cause borkage.
