-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Rout wrote:
On Mon, 24 Oct 2005 22:32:46 +0100
Jonathan Wright wrote:
- Second, run the digest command. You'll need to do this if it's not in
the standard portage tree and it's something you have added. Portage
needs to be told all the files within the tree and their md5 values, to
make sure nothing bad gets in :)
And by running emerge --digest target or ebuild target.ebuild digest
screws the digest system, because it substitutes the values you got from
the portage mirror with the values from the files on your computer. It
destroys any safety that the digest system offers.
So if someone has broken into your system and screwed around with the
portage tree so that when you install sylpheed-claws it does something
nasty, running the digest command will allow that to happen.
If the digests are wrong find out what the problem is!
My guess is that it didn't even get to the digest checks when it gave
me the error/warning. emerge --sync seems to have fixed the problem.
I probably should have tried that before posting. ;-)
- --
gentux
echo hfouvyAdpy/ofu | perl -pe 's/(.)/chr(ord($1)-1)/ge'
gentux's gpg fingerprint == 34CE 2E97 40C7 EF6E EC40 9795 2D81 924A
6996 0993
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDXWCsLYGSSmmWCZMRAhEwAJ4oplvQ41TfWsYJL9DmY6DGJ6dvHQCgi/Us
wpUly/Hz/3VTvZdFE7k1ILI=
=7dn/
-END PGP SIGNATURE-
--
gentoo-user@gentoo.org mailing list
