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 1Ri6ok-0004QW-C7 for garchives@archives.gentoo.org; Tue, 03 Jan 2012 16:02:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0423221C1B6; Tue, 3 Jan 2012 16:02:12 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id D6DEE21C083 for ; Tue, 3 Jan 2012 16:01:02 +0000 (UTC) Received: by werm12 with SMTP id m12so9768991wer.40 for ; Tue, 03 Jan 2012 08:01:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=+LdWoBWUCHx4x/P1fiPH5YS8FaprGZ/ZgQebbAH1GgE=; b=vA8jFZwsvCanhiMNmyBEcSqOGFULho6XfA9CxmH0/ASYVuX5G5SReTRHoa4Vg3bWqU nz16TccPL5Jn/Gpm+EaWQwz0DO1fsgQUP5yBMqsN+X+gcR7nmB7tBlIah2LskW8gHtys 0ysy+l2lHNWRb9BERoYfMy/USSlVWgYG56ziI= Received: by 10.216.132.20 with SMTP id n20mr34062303wei.54.1325606462105; Tue, 03 Jan 2012 08:01:02 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPS id ej17sm55212141wbb.14.2012.01.03.08.01.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 Jan 2012 08:01:01 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: (Was) Re: [gentoo-user] emerge --update behavior Date: Tue, 3 Jan 2012 16:00:52 +0000 User-Agent: KMail/1.13.7 (Linux/3.1.6-gentoo; KDE/4.7.3; x86_64; ; ) References: <4F00D521.1030702@orlitzky.com> <4F0316A0.7030304@gmail.com> <4F0316EA.9080405@gmail.com> In-Reply-To: <4F0316EA.9080405@gmail.com> 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 Content-Type: multipart/signed; boundary="nextPart25015390.xYAIayDPlF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201201031601.03473.michaelkintzios@gmail.com> X-Archives-Salt: 57ac89b5-3946-471a-afc3-9e35e53e24ef X-Archives-Hash: 80a3d49fbc2a383560665e4b9fd60180 --nextPart25015390.xYAIayDPlF Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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. > >>>=20 > >>> This was essentially Michal Mol's suggestion, and I gave an > >>> example where it would remove something important. > >>>=20 > >>>> 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. > >>>=20 > >>> This would be a suggestion to travel back in time and document > >>> something that I have no way of knowing now. > >>=20 > >> 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. > >=20 > > 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. :) > >=20 > > 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 >=20 > 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=20 a public key server, it seems likely that it has not propagated across the= =20 public servers yet and your enigmail plugin alerts you about it. =2D-=20 Regards, Mick --nextPart25015390.xYAIayDPlF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk8DJj8ACgkQVTDTR3kpaLZCdgCeKJ04RYXhezBa90QHFu/l7x9P m8AAn3HlwTgowrimrDZAlwbZi35eyK1z =j/oI -----END PGP SIGNATURE----- --nextPart25015390.xYAIayDPlF--