fetching verify failed ####################### 2010-09-07 10:31:54 (653 KB/s) - `/usr/portage/distfiles/GoogleEarthLinux-5.2.1.1547_beta.bin' saved [31406473/31406473] !!! Fetched file: GoogleEarthLinux-5.2.1.1547_beta.bin VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 31406473 !!! Expected: 31399370 ('Filesize does not match recorded size', 31406473, 31399370) Refetching... File renamed to '/usr/portage/distfiles/GoogleEarthLinux- 5.2.1.1547_beta.bin._checksum_failure_.qa_Ufx' !!! Couldn't download 'GoogleEarthLinux-5.2.1.1547_beta.bin'. Aborting. ^[[31;01m * ^[[39;49;00mFetch failed for 'sci-geosciences/googleearth-5.2.1.1547_beta', Log file: ^[[31;01m * ^[[39;49;00m '/var/log/portage/sci-geosciences:googleearth-5.2.1.1547_beta:20100907-083106.log' Reproducible: Always Steps to Reproduce:
Same problem here
same problem. I found other comments for similar bugs suggesting workarounds, but there isn't enough detail about how to do it. I tried "emerge --digest googleearth", which didn't work, and other comments like using "ebuild --force googleearth-5.2.1.1547_beta.ebuild manifest" or "repoman manifest" are poorly explained (eg how to use the commands).
Well, I solved the problem the ugly way: I modified the /usr/portage/sci-geosciences/googleearth/Manifest file, and I had the line: DIST GoogleEarthLinux-5.2.1.1547_beta.bin 31399370 RMD160 37ad0c000a50d1fc953c9570d75aac6b8673aa40 SHA1 8a11f50131901d647f82ff7c1eb075b076bf9463 SHA256 dbe73f8deaaeb9e4354594c13693bb0290160745ba7e68b708dbadb80250ff11 become: DIST GoogleEarthLinux-5.2.1.1547_beta.bin 31406473 RMD160 181ed85cb057a2c2eca97f28c07bcda40a2fa0da SHA1 75a458be01c331ac6d4dcd29f91d562fc3dfc604 SHA256 2e6fcbd2384446e2a6eed8ca23173e32c5f3f9ae4d1168e2e348c3924fd2bf30 It then installed. But it would crash. Having read about the qt-bundled flag beeing enabled by default because of frequent crashes and since I had it disabled on my system, I enabled it and got GoogleEarth up and running. But why on (Google)earth :-) is the Manifest not in sync with the downloaded file?
(In reply to comment #4) > But why on (Google)earth :-) is the Manifest not in sync with the downloaded > file? Because Google updates (bumps) the downloaded file without changing the URL, and the license doesn't allow us to mirror it on gentoo mirrors. So if it stops being in sync, a bump has to be done. Bumped to 5.2.1.1588, please sync.