For the last several days, this has been an issue: >>> Downloading 'http://dl.google.com/earth/client/current/GoogleEarthLinux.bin' ... ('Filesize does not match recorded size', 25606194L, 25602325) !!! Fetched file: GoogleEarthLinux-5.0.11729.1014.bin VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 25606194 !!! Expected: 25602325 I've resynchronized my Portage tree several times over the last several days.
(In reply to comment #0) > For the last several days, this has been an issue: > > >>> Downloading 'http://dl.google.com/earth/client/current/GoogleEarthLinux.bin' > ... > ('Filesize does not match recorded size', 25606194L, 25602325) > !!! Fetched file: GoogleEarthLinux-5.0.11729.1014.bin VERIFY FAILED! > !!! Reason: Filesize does not match recorded size > !!! Got: 25606194 > !!! Expected: 25602325 > > I've resynchronized my Portage tree several times over the last several days. Google released new version of Google Earth: http://www.gearthblog.com/blog/archives/2009/05/new_google_earth_50_update_version.html
New version is 5.0.11733.9347...
I'm having the same problem: 2009-05-10 23:50:26 (600 KB/s) - `/usr/portage/distfiles/GoogleEarthLinux-5.0.11729.1014.bin' saved [25606194/25606194] ('Filesize does not match recorded size', 25606194L, 25602325) !!! Fetched file: GoogleEarthLinux-5.0.11729.1014.bin VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 25606194 !!! Expected: 25602325 Refetching... File renamed to '/usr/portage/distfiles/GoogleEarthLinux-5.0.11729.1014.bin._checksum_failure_.uqqz3i' !!! Couldn't download 'GoogleEarthLinux-5.0.11729.1014.bin'. Aborting. * Fetch failed for 'x11-misc/googleearth-5.0.11729.1014', Log file: * '/var/tmp/portage/x11-misc/googleearth-5.0.11729.1014/temp/build.log'
I don't see a way to request a specific version from Google; they do not allow listing the contents of the download directory. I assume Gentoo refuses to mirror Google Earth because of licensing issues. If I (or some other person) mirror Google Earth releases on my server and assign version numbers to the files, could Gentoo's googleearth ebuilds point to my web server? This is one solution to this problem.
*** Bug 269480 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > I don't see a way to request a specific version from Google; they do not allow > listing the contents of the download directory. > > I assume Gentoo refuses to mirror Google Earth because of licensing issues. > > If I (or some other person) mirror Google Earth releases on my server and > assign version numbers to the files, could Gentoo's googleearth ebuilds point > to my web server? This is one solution to this problem. > google will kill your cat if you mirror their software on your server. since the version of google-earth that you download is not predictable, imo the logical step is to create a -9999 ebuild for the app. otherwise each time they release a new revision, installation fails.
the ebuild from portage tree still fails, is there a chance that this will be fixed?
Please fix this, verfication fails as mentioned by OP. Else, remove this from portage.
(In reply to comment #8) > Please fix this, verfication fails as mentioned by OP. Else, remove this from > portage. > same here... I have been trying this for a couple of days and no luck.
Since nobody fixed this yet for a quick workaround edit /usr/portage/x11-misc/googleearth/Manifest Change the corresponding line with the one given below. DIST GoogleEarthLinux-5.0.11729.1014.bin 25606194 RMD160 ba61c88c38eefad655cf0de4b17f033640783a2c SHA1 4aa2b565523dc6ee9592a0f96760297fc06f762c SHA256 fde44633607cb762810e14e8fe7c9755a1c9b04c10fbb712c2ab899274716b9a Emerged fine after the change.
This is a duplicate of bug 236400
For the impatient I would suggest doing: mkdir /usr/local/portage/x11-misc/googleearth cd /usr/local/portage/x11-misc/googleearth cp /usr/portage/x11-misc/googleearth/googleearth-5.0.11729.1014.ebuild ./googleearth-5.0.11733.9347.ebuild ebuild googleearth-5.0.11733.9347.ebuild digest emerge -av googleearth and to close this bug and finally wait for Bug 270895 to be closed. ;)
(In reply to comment #2) > New version is 5.0.11733.9347... It's in the tree. And I removed the older 5.* ebuilds with the same SRC_URI. That doesn't stop the problem but should be a good indication that the version has changed and a bump is required.