x11-misc/googleearth-4 can't be downloaded due to wrong filesize. >>> Emerging (1 of 1) x11-misc/googleearth-4 to / >>> Downloading 'http://dl.google.com/earth/GE4/GoogleEarthLinux.bin' --23:16:40-- http://dl.google.com/earth/GE4/GoogleEarthLinux.bin => `/usr/portage/distfiles/GoogleEarthLinux.bin' Resolving dl.google.com... 209.85.135.91 Connecting to dl.google.com|209.85.135.91|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 23.852.601 (23M) [application/octet-stream] 100%[====================================================================================================================>] 23.852.601 238.15K/s ETA 00:00 23:18:20 (232.72 KB/s) - `/usr/portage/distfiles/GoogleEarthLinux.bin' saved [23852601/23852601] ('Filesize does not match recorded size', 23852601L, 21607408) !!! Fetched file: GoogleEarthLinux.bin VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 23852601 !!! Expected: 21607408 Removing corrupt distfile... !!! Couldn't download 'GoogleEarthLinux.bin'. Aborting. !!! Fetch for /usr/portage/x11-misc/googleearth/googleearth-4.ebuild failed, continuing... !!! Some fetch errors were encountered. Please see above for details. x11-misc/googleearth-4
There's nothing like retarded upstream changing versions without changing the filename. :X
I think so but someday a part of this bigger file could also be a piece of software which I don't like to have on my computer. So I think it's better to report such errors. :X
I just want to add that an `ebuild googleearth-4.ebuild digest` doesn't help. I'm still getting the same error.
For me: ebuild /usr/portage/x11-misc/googleearth/googleearth-4.ebuild digest solves the file mismatch issue. But after that bug 177984 comes up, wich is imho due to changes in the .bin file.
The problem is that this error message doesn't seem to come from portage but from wget (I'm not quite sure in this point) and this file is not saved in /usr/portage/distfiles as it is done with any other files downloaded by wget if it's invoked by emerge.
*** Bug 179318 has been marked as a duplicate of this bug. ***
Created attachment 120043 [details] Google Earth 4.1 ebuild Pretty much edited around the problems with the postinit scripts causing access violation errors. I must have spent about three hours trying to hack around them before figuring out it would be much easier to let the ebuild insert them. :(
wow, I wonder why I did not have this simple idea. Thank you very much, committed :)
Shouldn't the ebuild to bumped to 4.1? This is a new version after all.
This thing cannot be bumped because the tarball always has the same name. So when you update you need to update yourself manually. An automatic update cannot work because the old download will be too big and portage will abort or portage will try to resume on top of the old tarball and fail the md5 check. Really portage does not have support for such an update and thus it needs to be done manually.
Okay, so to be clear, what a user needs to do is unmerge (emerge -C) and then emerge googleearth?
No, a user needs to remove the distfile and then remerge googleearth
*** Bug 180043 has been marked as a duplicate of this bug. ***
