According to http://www.google.com/earth/index.html they have a version newer than the one in portage
Thanks for the version bump notice. Assigning to maintainer
Another version bump, or a re-digest is needed. Best wishes, Anthony Staines >>> Emerging (2 of 2) sci-geosciences/googleearth-5.2.1.1588 * Fetching files in the background. To view fetch progress, run * `tail -f /var/log/emerge-fetch.log` in another terminal. >>> Downloading 'http://dl.google.com/earth/client/current/GoogleEarthLinux.bin' --2011-01-02 21:46:46-- http://dl.google.com/earth/client/current/GoogleEarthLinux.bin Resolving dl.google.com... 66.102.13.91, 66.102.13.93, 66.102.13.136, ... Connecting to dl.google.com|66.102.13.91|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 33589497 (32M) [application/octet-stream] Saving to: `/usr/portage/distfiles/GoogleEarthLinux-5.2.1.1588.bin' 100%[===========================================================================================================================>] 33,589,497 54.5K/s in 7m 40s 2011-01-02 21:54:26 (71.4 KB/s) - `/usr/portage/distfiles/GoogleEarthLinux-5.2.1.1588.bin' saved [33589497/33589497] ('Filesize does not match recorded size', 33589497L, 31406473) !!! Fetched file: GoogleEarthLinux-5.2.1.1588.bin VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 33589497 !!! Expected: 31406473 Refetching... File renamed to '/usr/portage/distfiles/GoogleEarthLinux-5.2.1.1588.bin._checksum_failure_.8qzWjc' !!! Couldn't download 'GoogleEarthLinux-5.2.1.1588.bin'. Aborting. * Fetch failed for 'sci-geosciences/googleearth-5.2.1.1588', Log file: * '/var/tmp/portage/sci-geosciences/googleearth-5.2.1.1588/temp/build.log' * Wrong checksum or file size means that Google silently replaced the distfile with a newer version. * Note that Gentoo cannot mirror the distfiles due to license reasons, so we have to follow the bump. * Please file a version bump bug on http://bugs.gentoo.org (search existing bugs for googleearth first!). * By redigesting the file yourself, you will install a different version than the ebuild says, untested! >>> Failed to emerge sci-geosciences/googleearth-5.2.1.1588, Log file:
It seems that here is version 6 out there :)
*** Bug 350469 has been marked as a duplicate of this bug. ***
Hi, I have downloaded and the latest version of Google Earth successfully - little jumpy on the scroll, but thats on a HP laptop with a built-in Intel graphics card. How about tying the ebuild to draw down a fixed version rather than using the "latest" symbolic link. Cheers, Kev
Both versions currently in portage failed to build with checksum failure errors.
I agree, the current version is 6.0 (beta) and the current version only points to this version.
Trying to do a manual install, I get the following: Verifying archive integrity... All good. Uncompressing Google Earth for GNU/Linux 6.0.1.2032............................................................................................. This version of Google Earth requires LSB 4.0 support which you do not seem to have. later on, I get: ./googleearth: line 18: /home/googleearth/google-earth/googleearth-bin: No such file or directory ./googleearth: line 18: /home/googleearth/google-earth/googleearth-bin: Success Questions: 1. do we really need LSB 4.0 for GE 6.0+ ? 2. did my line 18 error result from a lack of LSB? 3. workarounds? TIA
(In reply to comment #8) > 3. workarounds? ln -s /lib/ld-linux.so.2 /lib/ld-lsb.so.3
YEP Works; Thank You!! How could I have diagnosed this on my own (Strace revealed nothing; ldd didn't work)? I'm guessing this soft link is known by the Gentoo community, and has fixed a number of other issues besides GE and ldd. Also, the link is to a 32-bit module - yet this is supposedly a 64-bit version of GE!? (thanks again)
Is it possible to match the correct file checksize for the latest binary so that all Gentoo users will be able to install googleearth without manual interference? This problems seems to be hanging around since a while... Thanks.
*** Bug 347431 has been marked as a duplicate of this bug. ***
Bumped, sorry for the waiting. I considered which package should install the symlink, and in the end got suggested to rewrite the interpreter path with patchelf.
