Bugzilla Bug 139544

basilio ~ # emerge googleearth
Calculating dependencies... done!

>>> Emerging (1 of 1) x11-misc/googleearth-4_beta to /
>>> checking ebuild checksums ;-)
>>> checking auxfile checksums ;-)
>>> checking miscfile checksums ;-)
>>> checking GoogleEarthLinux.bin
!!! Digest verification failed:
!!! /usr/portage/distfiles/GoogleEarthLinux.bin
!!! Reason: Filesize does not match recorded size
!!! Got: 17027325
!!! Expected: 16984110

I tried to truncate /usr/portage/distfiles/GoogleEarthLinux.bin to the expected
size 16984110, but that did not help, it just got me a "failed on MD5
verification" error.

Does this problem occur because the providers of Google Earth change the
contents of the download URL?

The file that gets downloaded to /usr/portage/distfiles claims to be version
4.0.1660 (for the time being).

(In reply to comment #1)
> Does this problem occur because the providers of Google Earth change the
> contents of the download URL?

Yes, sure... it would be nice if enough people complained to Google so that
they start to provide versioned tarballs like everyone else.

The same problem, happens on amd64 install 
>>> checking ebuild checksums ;-)
>>> checking auxfile checksums ;-)
>>> checking miscfile checksums ;-)
>>> checking GoogleEarthLinux.bin
!!! Digest verification failed:
!!! /usr/portage/distfiles/GoogleEarthLinux.bin
!!! Reason: Filesize does not match recorded size
!!! Got: 17027325
!!! Expected: 16984110

removing the ebuild and then sync doesnt solve  the problem.
i also tried to use the package from google;s website and it didnt work either.

thanks I have redigested it.

Guys, I know this ebuild is still masked, but perhaps we should leave this one
open.  

Is it possible to add a warning message in the ebuild to explain to users how
to get around this (i.e. create a new digest)?  IMO, the ebuild is still
"broken" if Google doesn't move to a versioned tarball as Jakub suggested.

*** Bug 140684 has been marked as a duplicate of this bug. ***

Broken again... Upstream should really improve their release hygiene. :P

Are we allowed to mirror them? Then we could add date-versioned files on our
servers or something like this.

(In reply to comment #8)
> Are we allowed to mirror them? Then we could add date-versioned files on our
> servers or something like this.

Unfortunately not. We did and upstream screamed. :/

no, we are not allowed to mirror it:

You agree
that you will not, and will not allow any third party
to, (i) copy, sell, license, distribute, transfer,
modify, adapt, translate, prepare derivative works
from, decompile, reverse engineer, disassemble or
otherwise attempt to derive source code from the
Software, unless otherwise permitted, ...

keyword being "distribute" here.
So just use emerge --digest when you come across this bug. Portage does not
allow always redownloading and not checking digests yet.

If you are a developer feel free to commit the new digest when this comes up
again. I just did fix this digest.

*** Bug 140875 has been marked as a duplicate of this bug. ***

And again. This is starting to be a huge PITA, anyone tried to contact Google
folks and give them a hint on doing civilized releases?

redigested again

I have mailed a friend at Google about this. Fingers crossed...

*** Bug 140985 has been marked as a duplicate of this bug. ***

*** Bug 147683 has been marked as a duplicate of this bug. ***

And again...

fixed

fixed

*** Bug 147889 has been marked as a duplicate of this bug. ***

*** Bug 150975 has been marked as a duplicate of this bug. ***

Guess what... :P

What?

Freshly downloaded distfile:

 * GoogleEarthLinux.bin MD5 ;-) ...                                       [ ok
]
 * GoogleEarthLinux.bin RMD160 ;-) ...                                    [ ok
]
 * GoogleEarthLinux.bin SHA1 ;-) ...                                      [ ok
]
 * GoogleEarthLinux.bin SHA256 ;-) ...                                    [ ok
]
 * GoogleEarthLinux.bin size ;-) ...                                      [ ok
]
 * checking ebuild checksums ;-) ...                                      [ ok
]
 * checking auxfile checksums ;-) ...                                     [ ok
]
 * checking miscfile checksums ;-) ...                                    [ ok
]
 * checking GoogleEarthLinux.bin ;-) ...                                  [ ok
]

...and it does not look like anyone touched the digest in past few days.

And again....

dont always reopen this bug. YOu also get digest mismatches when you dont have
the latest version of the tarball yourself.

Please remove /usr/portage/distfiles/GoogleEarthLinux.bin and try again prior
to posting here.

I am still hoping for upstream to change their tarball name for this one

Seems to be a long time ago, when this bug happened the last time, but I'm
think, it's the same problem:

emerge -va googleearth

[..]

>>> Emerging (1 of 1) x11-misc/googleearth-4.2.205.5730 to /
>>> Downloading 'http://dl.google.com/earth/client/current/GoogleEarthLinux.bin'

[..]

!!! Fetched file: GoogleEarthLinux.bin VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got:      20110357
!!! Expected: 23048189
Refetching... File renamed to
'/usr/portage/distfiles/GoogleEarthLinux.bin._checksum_failure_.Rg73kM'

!!! Couldn't download 'GoogleEarthLinux.bin'. Aborting.
 * Fetch failed for 'x11-misc/googleearth-4.2.205.5730'
!!! can't process invalid log file:
'/var/tmp/portage/x11-misc/googleearth-4.2.205.5730/temp/logging/merge'