I have some huge problems with sci-geosciences/googleearth-7.0.3.8542 (probably unrelated to gentoo, rather googleearth itself). I'd like to go back to the previous verion i had, which worked perfectly. I've masked >=7.0.0.0 but emerging 6.2.2 fails. I tried several times just to be sure it's not actually a download problem from my side. Reproducible: Always 29600K .......... .......... .......... .......... .......... 98% 1,32M 0s 29650K .......... .......... .......... .......... .......... 99% 1,31M 0s 29700K .......... .......... .......... .......... .......... 99% 1,32M 0s 29750K .......... .......... .......... .......... .......... 99% 1,31M 0s the relevant part of the log is: 29800K .......... .......... .......... .......... .......... 99% 1,31M 0s 29850K .......... .......... .......... .......... .......... 99% 1,32M 0s 29900K .......... .......... .......... .......... .......... 99% 1,31M 0s 29950K .. 100% 627K=23s 2013-03-28 23:06:37 (1,27 MB/s) - "/var/portage/distfiles/GoogleEarthLinux-6.2.2.6613_amd64.deb" salvato [30671794/30671794] !!! Fetched file: GoogleEarthLinux-6.2.2.6613_amd64.deb VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 30671794 !!! Expected: 25609162 Refetching... File renamed to '/var/portage/distfiles/GoogleEarthLinux-6.2.2.6613_amd64.deb._checksum_failure_.T9Oz4W' !!! 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' * Package: sci-geosciences/googleearth-6.2.2.6613 * Repository: gentoo * Maintainer: hasufell@gentoo.org
That's expected. Google does not name the tarball properly, so checksum failure just means that they bumped the version and also means you cannot go back to older ones until you find that old tarball somewhere on the internet.
er... sure, but there's still this ebuild in portage and that's really confusing then. I understand that's all google's fault and all, but still, i consider this a bug in portage. Juste remove those or rename the ebuild something like googleearth-bin-9999 ??
(In reply to comment #2) > er... sure, but there's still this ebuild in portage and that's really > confusing then. There is a message in pkg_nofetch. > I understand that's all google's fault and all, but still, i consider this a > bug in portage. Juste remove those or rename the ebuild something like > googleearth-bin-9999 ?? No, that is wrong. Live ebuilds are repository-based. Old googleearth ebuilds are just kept for people who happen to have those old tarballs and need them.