public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gentuxx <gentuxx@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Um...Who can fix this? -- SOLVED
Date: Mon, 24 Oct 2005 15:31:08 -0700	[thread overview]
Message-ID: <435D60AC.5000302@gmail.com> (raw)
In-Reply-To: <20051025111033.C761.NICK@rout.co.nz>

-----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



  reply	other threads:[~2005-10-24 22:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 21:06 [gentoo-user] Um...Who can fix this? gentuxx
2005-10-24 21:23 ` Christoph Gysin
2005-10-24 21:32 ` Jonathan Wright
2005-10-24 21:56   ` gentuxx
2005-10-24 22:16   ` Nick Rout
2005-10-24 22:31     ` gentuxx [this message]
2005-10-24 22:53       ` [gentoo-user] Um...Who can fix this? -- SOLVED Ciaran McCreesh
2005-10-24 23:33     ` [gentoo-user] Um...Who can fix this? Jonathan Wright
2005-10-24 23:54       ` Nick Rout
2005-10-25  0:02         ` Ciaran McCreesh
2005-10-25  0:16           ` Nick Rout
2005-10-25  0:42             ` Ciaran McCreesh
2005-10-25  0:07         ` Holly Bostick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=435D60AC.5000302@gmail.com \
    --to=gentuxx@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox