!!! Fetched file: GoogleEarthLinux-6.2.2.6613_amd64.deb VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 30726902 !!! Expected: 25609162 Refetching... File renamed to '/mnt/distfiles/GoogleEarthLinux-6.2.2.6613_amd64.deb._checksum_failure_.Qt30nr' !!! Couldn't download 'GoogleEarthLinux-6.2.2.6613_amd64.deb'. Aborting. * Fetch failed for 'sci-geosciences/googleearth-6.2.2.6613', Log file: * '/var/tmp/portage/sci-geosciences/googleearth-6.2.2.6613/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! Reproducible: Always Steps to Reproduce: 1.emerge googleearth 2. 3. Actual Results: fetch fails Expected Results: fetch suceeds badly written closed-source software is evil.
Same failure here: === >>> Emerging (2 of 2) sci-geosciences/googleearth-6.2.2.6613 >>> Downloading 'http://dl.google.com/dl/earth/client/current/google-earth-stable_current_amd64.deb' --2012-11-12 11:30:21-- http://dl.google.com/dl/earth/client/current/google-earth-stable_current_amd64.deb Resolviendo dl.google.com (dl.google.com)... 173.194.34.206, 173.194.34.194, 173.194.34.199, ... Conectando con dl.google.com (dl.google.com)[173.194.34.206]:80... conectado. Petición HTTP enviada, esperando respuesta... 200 OK Longitud: 30726902 (29M) [application/x-debian-package] Grabando a: “/usr/portage/distfiles/GoogleEarthLinux-6.2.2.6613_amd64.deb” 100%[======================================>] 30.726.902 9,55MB/s en 3,1s 2012-11-12 11:30:24 (9,55 MB/s) - “/usr/portage/distfiles/GoogleEarthLinux-6.2.2.6613_amd64.deb” guardado [30726902/30726902] !!! Fetched file: GoogleEarthLinux-6.2.2.6613_amd64.deb VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 30726902 !!! Expected: 25609162 Refetching... File renamed to '/usr/portage/distfiles/GoogleEarthLinux-6.2.2.6613_amd64.deb._checksum_failure_.Q94cu2' !!! Couldn't download 'GoogleEarthLinux-6.2.2.6613_amd64.deb'. Aborting. * Fetch failed for 'sci-geosciences/googleearth-6.2.2.6613', Log file: * '/var/tmp/portage/sci-geosciences/googleearth-6.2.2.6613/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! ===
And here too.
Still no news on this? Currently it's impossible to install the latest googleearth version in the tree.
Same here. Bug still exists..... !!! Fetched file: GoogleEarthLinux-6.2.2.6613_amd64.deb VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 30726902 !!! Expected: 25609162
does not CC arch teams, please
Reverted component change, "Ebuilds" is only for "adding new ebuilds", not for "problems with ebuilds"; as stated by the description of the component. > Still no news on this? If the maintainer is not around for some time you can manually do: `ebuild /usr/portage/sci-geosciences/googleearth/googleearth-6.2.2.6613 manifest` Please update this bug letting us know whether that results in a working Google Earth; if not, the maintainer needs to do much more than just updating the manifest.
Comments in ebuild says: # incorrect digest means upstream bumped and thus needs version bump So, we should wait for maintainer to fix it properly via bump
Still the same bug ! Just synced portage tree
I solved this problem, got googleearth starting! Steps to fix it: 1. Re-digest the file by yourself: cd /usr/portage/sci-geosciences/googleearth/ delete all older ebuilds,but keep the current "googleearth-.2.2.6613.ebuild" delete the Manifest-file ebuild googleearth-6.2.2.6613.ebuild digest 2. emerge googleearth 3. delete Symlink /etc/fonts/conf.d/65-fonts-persian.conf This worked for me, googleearth is running very smooth.
Second time, please do not CC arch teams for no reason. If you want to make the bug specific to a certain arch, you can specify that arch as the platform field of the bug (the reporter can do so, as well as people that have edit privileges) which I have done for you in this case. The arch teams should only be involved when testing on a certain arch needs to be done; and perhaps some other reasons as well, but I don't see one that fits in this situation.
> Second time, please do not CC arch teams for no reason. > > If you want to make the bug specific to a certain arch, you can specify that > arch as the platform field of the bug (the reporter can do so, as well as > people that have edit privileges) which I have done for you in this case. > > The arch teams should only be involved when testing on a certain arch needs > to be done; and perhaps some other reasons as well, but I don't see one that > fits in this situation. Ok, thanks Tom. I'm new in bugs.gentoo.org, now I realized it.
The recipe of Chris works for me too. Especially the removal /etc/fonts/conf.d/65-fonts-persian.conf was necessary. I found that this link belongs to fontconfig-2.9.0. Thus, I am afraid, that the next 'emerge fontconfig' will create it again.
Nearly a month later and no change yet
See bug #455124 for the /etc/fonts/conf.d/65-fonts-persian.conf crash issue. *** This bug has been marked as a duplicate of bug 351817 ***
