Neil Bothwick schreef: > On Tue, 25 Oct 2005 20:51:14 -0400, Michael W. Holdeman wrote: > > >> I then rearchive kdepim-3.4.92.tar.bz2 and run ebuild >> /usr/portage/kde-base/kdepim/kdepim-3.5.0_beta2.ebuild digest, >> which completes successfully but when attempting to emerge >> korganizer again I get !!! Digest verification Failed: !!! >> /usr/portage/distfiles/kdepim-3.4.92.tar.bz2 !!! Reason: Failed on >> MD5 verification > > > >> what did I miss? > > > Recreating the digest for the package. Portage uses MD5 checksums to > check that files have not been altered, as a security measure. You > need to regenerate the digest as you made the changes and want to > accept them. > > Either "ebuild /path/to/ebuild digest" or "emerge --digest > --other-options package" > >
Should this be handled in /usr/portage in any case? Portage is going to overwrite the changed files (the digest) every time a sync is done, isn't it? I wonder if this digest being created in the real Portage tree rather than the overlay tree might not be the problem in the first place-- since changed files in the Portage tree itself 'should' automatically fail, since that's what the check function is designed to keep an eye on. It really doesn't do much good for a file to be changed in the official Portage tree and for Portage to just say "OK, that's fine." Suppose you'd been hacked? The overlay tree, on the other hand, is designed to accept modified files; that's what it's for. I'd copy *both* ebuilds to my overlay tree and digest the copies, and see if that helped. Does the digest for the parent application digest the hard dependencies? Silly question, of course it must. So that's what's failing, the korganizer digest of kdepim, not the kdepim digest itself; we never get that far. So korganizer has to be redigested as well. Holly -- gentoo-user@gentoo.org mailing list
