4.2 is out. I tried to find a direct download link but couldn't. Any way the file name is the same so I think we probably should fetch restrict this one and tell people to rename the file.
It's allready bumped, digests of current googleearth in Portage matches the 4.2 release.
*** This bug has been marked as a duplicate of bug 189827 ***
(In reply to comment #1) > It's allready bumped, digests of current googleearth in Portage matches the 4.2 > release. > I checked with the integrated update manager and it's not the latest version: Currently installed version: 4.1.7076.4458 New version: 4.2.180.1134
well then do it better and commit what you think is needed. I have the right version in my about screen.
Google's habit of naming the files the same irrespective of the version makes things difficult. I think the only way to make sure the latest version is installed is to remove the old file from /usr/portage/distfiles before (re)running 'emerge googleearth'. I know it's an ugly hack, but can it be done via the ebuild?
(In reply to comment #5) > I think the only way to make sure the latest version is > installed is to remove the old file from /usr/portage/distfiles before > (re)running 'emerge googleearth'. I know it's an ugly hack, but can it be done > via the ebuild? No, this no way can be done via ebuild. Complain to Google.
May I perhaps suggest to change the gentoo version number (at least the -r? number) whenever the digest changes? This way one would get informed when a new googleearth version is out. Especially for computers which can be online only temporary, it is rather annoying if one only sees during emerge -e world that one should have downloaded a new version of googleearth. You might still keep the previous ebuild in the tree for a while (even if - as I suppose - the digest must change also for the previous version) so that people not wanting to upgrade can then simply mask the new version and do not need to emerge/download it unless they explicitly require it.
(In reply to comment #7) You cannot have multiple different checksums for identically named file, won't work. So no, you cannot have multiple ebuild versions in the tree ATM either. The only solution is to finally stick RESTRICT=fetch into the ebuild and let people rename the file after download.
Ok, since this bug is reopened and noone seems to take notice of bug #189827 I'll summarize what I posted there: 1) The current version number is 4.2, not 4. Please rename the ebuild. See #189827 for reasons 2) There IS a direct link to the current version, http://dl.google.com/earth/client/GE4/release2/GoogleEarthLinux.bin For your file problem: Exploit bug #174704 and append ?gentooversion=4.2 to the URL. Google's webserver doesn't mind but you avoid the problem with distfiles/.
*** Bug 192255 has been marked as a duplicate of this bug. ***
cd /usr/portage/distfiles rm GoogleEarth* wget http://dl.google.com/earth/client/GE4/release2/GoogleEarthLinux.bin cd /usr/portage/x11-misc/googleearth/ ebuild googleearth-4.ebuild digest Works. Ebuild is still borked due to wrong file download.... Hopefully mirrors will refresh shortly?
While version bump on the ebuild would be nice, purging /usr/portage/distfiles/GoogleEarthLinux.bin and re-emerging does the trick for me. :)
I noticed emerge now handles wrong digests intelligently with renaming and refetching. The emerge is no longer aborted and the user no longer annoyed, so I just went ahead and use the full version number from now on :) Have fun with it!
