Gentoo Archives: gentoo-user

From: Mick <michaelkintzios@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: (Was) Re: [gentoo-user] emerge --update behavior
Date: Tue, 03 Jan 2012 16:02:26
Message-Id: 201201031601.03473.michaelkintzios@gmail.com
In Reply to: Re: (Was) Re: [gentoo-user] emerge --update behavior by Michael Mol
1 On Tuesday 03 Jan 2012 14:55:38 Michael Mol wrote:
2 > Michael Mol wrote:
3 > > Hinnerk van Bruinehsen wrote:
4 > >> On 02.01.2012 18:58, Michael Orlitzky wrote:
5 > >>> On 01/02/12 12:47, Mark Knecht wrote:
6 > >>>> Again, 'equery depends' will tell you if any package locatable
7 > >>>> through the @world hierarchy needs the package. No need to
8 > >>>> uninstall anything to do that level of investigation.
9 > >>>> revdep-rebuild -I is also useful, although more historically than
10 > >>>> now.
11 > >>>
12 > >>> This was essentially Michal Mol's suggestion, and I gave an
13 > >>> example where it would remove something important.
14 > >>>
15 > >>>> Really, the proposal to 'fix --update' doesn't address really
16 > >>>> knowing what your system is running and why. Get to the root of
17 > >>>> that and the --update thing becomes the non-issue that many of us
18 > >>>> think it is.
19 > >>>
20 > >>> This would be a suggestion to travel back in time and document
21 > >>> something that I have no way of knowing now.
22 > >>
23 > >> You could create your own overlay with "meta"-ebuilds, e. g.
24 > >> system-maintenance, customer1, customer2.
25 > >> Inside the ebuilds you define depends on the packages the customer
26 > >> wants. Doing so you could wipe everything except the "meta"-ebuilds
27 > >> from world. When a customer quits you can unmerge his or her
28 > >> "meta"-ebuild and depclean.
29 > >> If you add everything needed to the respective "meta"-ebuild, you'll
30 > >> always be on the safe side.
31 > >
32 > > Getting EnigMail set up on a Seamonkey/Win7 box, and Enigmail is
33 > > complaining that your signature is unverified. I don't know/understand
34 > > PGP/GPG all that well, but I think this is something you're supposed to
35 > > be able to fix on your end. If that's not the case, let me know, and
36 > > I'll get it fixed on my end. :)
37 > >
38 > > gpg command line and output:
39 > > C:\Program Files (x86)\GNU\GnuPG\gpg.exe
40 > > gpg: Signature made 01/03/12 09:05:56 using RSA key ID 8D16461C
41 > > gpg: Can't check signature: public key not found
42 >
43 > Doh...that was supposed to go directly to Hinnerk. "Reply to sender
44 > only" my hind leg...
45
46 Looks like a recently created gpg key. Assuming the owner has uploaded it to
47 a public key server, it seems likely that it has not propagated across the
48 public servers yet and your enigmail plugin alerts you about it.
49 --
50 Regards,
51 Mick

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: (Was) Re: [gentoo-user] emerge --update behavior Michael Mol <mikemol@×××××.com>
Re: (Was) Re: [gentoo-user] emerge --update behavior Michael Mol <mikemol@×××××.com>