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 <gentoo-user+bounces-133277-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1Ri88F-0007Yn-M2
for garchives@archives.gentoo.org; Tue, 03 Jan 2012 17:26:39 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 4997221C083;
Tue, 3 Jan 2012 17:26:25 +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 9F58821C083
for <gentoo-user@lists.gentoo.org>; Tue, 3 Jan 2012 17:25:19 +0000 (UTC)
Received: by ghrr19 with SMTP id r19so6641693ghr.40
for <gentoo-user@lists.gentoo.org>; Tue, 03 Jan 2012 09:25:19 -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=3cn8/69X1r+ytCTDE3dzlMoqKjjvkzxmWVE6n7iLMs8=;
b=qegWIBL7AzYTOuHwZduduKk6udfZbH3Frt/gBrvIe+p+TwKieOwgWDhgbxckX8Sh36
pbyoNBpJYufQkfibcvqK3aGHmP4Sp2YtqTz7u8TQYS30osgeAq6MaoU49gI//oviU3RC
Wo/QjBNABpMf5uDsYAV0VgLdy1pfDRWbuYLPk=
Received: by 10.236.9.106 with SMTP id 70mr26269438yhs.118.1325611519120;
Tue, 03 Jan 2012 09:25:19 -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 j25sm75372410yhm.12.2012.01.03.09.25.17
(version=SSLv3 cipher=OTHER);
Tue, 03 Jan 2012 09:25:18 -0800 (PST)
Message-ID: <4F0339FB.80504@gmail.com>
Date: Tue, 03 Jan 2012 12:25:15 -0500
From: Michael Mol <mikemol@gmail.com>
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: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
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: 18fce8ae-8044-4905-ac51-c103a3792c98
X-Archives-Hash: 74ccd0d45894e10c68c0375e7c9d786a
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.
Found most of the problem; Enigmail defaulted to an empty "automatically
download keys for signature vereification from the following keyserver"
field. Fixed that, and things started working a little better. (Herr Van
Bruinehsen's key doesn't seem to have propagated, yes, but now yours
works fine. :) )