Michel Merinoff <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Fri, 01 Sep 2006 01:44:14 +0400:
> Oliver Klein wrote: >> So i decide to install dev-libs/atk but this tells me >> >> >> !!! Digest verification failed: >> !!! /usr/portage/distfiles/atk-1.12.1.tar.bz2 >> !!! Reason: Filesize does not match recorded size >> !!! Got: 641378 >> !!! Expected: 632397 >> >> So please can anyone help me to install firefox? >> > In this case, I often did something like ebuild > </usr/portage/dev-libs/atk(blah-blah).ebuild> digest. I had broken > digest even after unpacking the latest snapshot of portage tree. The problem with digest is that it makes anything there look right to portage, whether it is or not. If you change something in an ebuild or the sources tarball, it's appropriate to use ebuild digest because you know where the changes came from. If you didn't, then for all you know, the difference is due to some cracker trying to insert his own malware. Sure, it's most likely just a mistake, or possibly a download error (in which case you want to redownload rather than force portage to ignore the error), but the point is, portage has those checks there for a reason, and if you bypass them, unless you made or verified the changes yourself, you have no idea whether the change is a harmless error, a bad download that will break the merge or harm package functionality after merge, or a cracker trying to insert malware. That's a risk you can take if you want, but it's not one I choose to take! Even if that means filing a bug and waiting a few days for a fix, that's what I'll do! -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
