Alan McKinnon wrote: > On Tuesday 19 December 2006 14:10, Dale wrote: > > >> It seems to be thinking it is getting a bad download. Is this a bug >> or is it just me? It does the same thing each time, downloads it >> then pukes it out. Since I am on this slow dial-up and it takes >> about 2 hours for this download, I would rather it either like it or >> stop trying. :-/ I do have it installed though and it is pretty >> cool. ;-) >> >> If it is a bug, I'll file it. I just want to make sure it is not >> just me. >> >> Dale >> > > I also get this every now and then, often with proprietary packages. If > google were to patch and recompile without changing version numbers. > then this would happen as the binary size and MD5 no longer match. Or, > it could be wrong data in portage. Try resync and try again. If that > doesn't work, you could always check that the download is correct by > comparing with google's published md5 and "fixing" your local portage > tree: > > ebuild /path/to/googleearth/ebuild digest > ebuild /path/to/googleearth/ebuild manifest > > alan > Looks like Google would let distros mirror the thing so that versions and security measures can be used without causing trouble like this. I mean after all, I have went through this download about three or four times now. Since it is getting it from Google's site, I'm sure it is a good copy, not to mention it works well. Then again, Google has such a massive number of servers they likely don't even notice I am downloading again and again, well, they may see someone with a really slow connection connected for a couple hours.
I also did a emerge --digest googleearth but it seems to only work once. Not sure what the deal is there. I'm also glad I didn't file a bug now too. Dale :-) :-) :-)
