From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ri75i-0000KN-6p for garchives@archives.gentoo.org; Tue, 03 Jan 2012 16:19:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8F84A21C149; Tue, 3 Jan 2012 16:19:44 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 6A90B21C03F for ; Tue, 3 Jan 2012 16:18:24 +0000 (UTC) Received: by ghrr19 with SMTP id r19so6594051ghr.40 for ; Tue, 03 Jan 2012 08:18:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iBeGkrjTbCjzJpTvsKasaBhFeyxqX/f9ftJSL3gaDXw=; b=qbFN2wQLvoZ7JuTkfLIkWgIkGvCkq9+vpyVlyp9PDIpjw7guc7qylAetufhBZvFbIi b2V/JxHGMhFRETvvZq58iJn9hfvUQ1GM3C7maPzio6L3J9a8vcEB/9U3EE6YrArGFtw2 8/EDdqq4H2g+yl61JGmmD0L7TPFb6TTfjF1BQ= Received: by 10.101.61.14 with SMTP id o14mr14705058ank.33.1325607503915; Tue, 03 Jan 2012 08:18:23 -0800 (PST) Received: from [192.168.9.92] (adsl-76-236-174-54.dsl.klmzmi.sbcglobal.net. [76.236.174.54]) by mx.google.com with ESMTPS id u9sm109279594anh.20.2012.01.03.08.18.21 (version=SSLv3 cipher=OTHER); Tue, 03 Jan 2012 08:18:22 -0800 (PST) Message-ID: <4F032A4C.1000906@gmail.com> Date: Tue, 03 Jan 2012 11:18:20 -0500 From: Michael Mol User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20111221 Firefox/9.0.1 SeaMonkey/2.6.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: (Was) Re: [gentoo-user] emerge --update behavior References: <4F00D521.1030702@orlitzky.com> <4F0316A0.7030304@gmail.com> <4F0316EA.9080405@gmail.com> <201201031601.03473.michaelkintzios@gmail.com> In-Reply-To: <201201031601.03473.michaelkintzios@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: b5f0f962-e11e-4420-881e-2994d985703b X-Archives-Hash: 712c137d69a7904c1a821dcc3ffc163b Mick wrote: > On Tuesday 03 Jan 2012 14:55:38 Michael Mol wrote: >> Michael Mol wrote: >>> Hinnerk van Bruinehsen wrote: >>>> On 02.01.2012 18:58, Michael Orlitzky wrote: >>>>> On 01/02/12 12:47, Mark Knecht wrote: >>>>>> Again, 'equery depends' will tell you if any package locatable >>>>>> through the @world hierarchy needs the package. No need to >>>>>> uninstall anything to do that level of investigation. >>>>>> revdep-rebuild -I is also useful, although more historically than >>>>>> now. >>>>> >>>>> This was essentially Michal Mol's suggestion, and I gave an >>>>> example where it would remove something important. >>>>> >>>>>> Really, the proposal to 'fix --update' doesn't address really >>>>>> knowing what your system is running and why. Get to the root of >>>>>> that and the --update thing becomes the non-issue that many of us >>>>>> think it is. >>>>> >>>>> This would be a suggestion to travel back in time and document >>>>> something that I have no way of knowing now. >>>> >>>> You could create your own overlay with "meta"-ebuilds, e. g. >>>> system-maintenance, customer1, customer2. >>>> Inside the ebuilds you define depends on the packages the customer >>>> wants. Doing so you could wipe everything except the "meta"-ebuilds >>>> from world. When a customer quits you can unmerge his or her >>>> "meta"-ebuild and depclean. >>>> If you add everything needed to the respective "meta"-ebuild, you'll >>>> always be on the safe side. >>> >>> Getting EnigMail set up on a Seamonkey/Win7 box, and Enigmail is >>> complaining that your signature is unverified. I don't know/understand >>> PGP/GPG all that well, but I think this is something you're supposed to >>> be able to fix on your end. If that's not the case, let me know, and >>> I'll get it fixed on my end. :) >>> >>> gpg command line and output: >>> C:\Program Files (x86)\GNU\GnuPG\gpg.exe >>> gpg: Signature made 01/03/12 09:05:56 using RSA key ID 8D16461C >>> gpg: Can't check signature: public key not found >> >> Doh...that was supposed to go directly to Hinnerk. "Reply to sender >> only" my hind leg... > > Looks like a recently created gpg key. Assuming the owner has uploaded it to > a public key server, it seems likely that it has not propagated across the > public servers yet and your enigmail plugin alerts you about it. Mick, yours gives me the same error: gpg command line and output: C:\Program Files (x86)\GNU\GnuPG\gpg.exe gpg: Signature made 01/03/12 11:01:03 using DSA key ID 792968B6 gpg: Can't check signature: public key not found Though trying querying for 8D16461C or 792968B6 at pool.sks-keyservers.net or subkeys.pgp.net gives me "no key found" errors.