public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Munat <bent@munat.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] prioritising security updates
Date: Wed, 07 Sep 2005 09:21:21 -0700	[thread overview]
Message-ID: <431F1381.7020505@munat.com> (raw)
In-Reply-To: <200509070751.42658.jaervosz@gentoo.org>

Sune Kloppenborg Jeppesen wrote:
> On Wednesday 07 September 2005 04:04, Ben Munat wrote:
> 
>>So, how do I wind up with 17 packages that need to be updated? Hmm, perhaps
>>these are all packages on my system that are neither in my world file nor
>>depdencies of stuff in my world file? Would that then make them orphaned?
>>And theoretically safe to delete? How does one find out if a specific
>>package is required by any other packages again?
> 
> Only packages you explicitly emerge are recorded in the world profile 
> (/var/lib/portage/world) dependencies are not. See the man pages for portage 
> and emerge for more details.
> 
> HTH
> 

Thanks... however, I knew this much -- found that I have to be careful with this when 
getting going on a new gentoo system. It's handy to say "emerge somephpapp" and get php 
and mysql in the process... except then they're not in my world file.... though I suppose 
I can always just add them by hand.

But doing an "emerge -D world" should find any dependencies of anything in the world file 
that need updating, right? So, my questions still stand: are these packages that 
glsa-check is finding stuff that other packages depended on at one point -- so they got 
pulled in -- but are now no longer needed? And what tool can I use to ascertain this? 
"emerge --depclean" is basically useless... it always wants to uninstall things that I'm 
fairly sure are needed. "etcat" doesn't seem to have anything for finding dependecies. And 
"equery depends" is still "unimplemented"... (though I thought I'd used that at one point 
but it seems to find no results for everything I try).

Ideas anyone? What do you use to keep orphaned packages off your system?

b
-- 
gentoo-server@gentoo.org mailing list



  reply	other threads:[~2005-09-07 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 22:05 [gentoo-server] prioritising security updates Christopher Schwerdt
2005-09-06 22:16 ` Jeremy Brake
2005-09-07  2:04 ` Ben Munat
2005-09-07  5:51   ` Sune Kloppenborg Jeppesen
2005-09-07 16:21     ` Ben Munat [this message]
2005-09-13 22:26       ` Jonas 'data' Fietz
2005-09-21 16:45         ` Yogesh Sharma
2005-09-22  3:28           ` Ben Munat
2005-09-22  4:24             ` Yogesh Sharma
2005-09-22 16:03               ` Ben Munat
  -- strict thread matches above, loose matches on Subject: below --
2005-09-06  0:09 [gentoo-server] Virtual ssh users Yogesh Sharma
2005-09-06  0:26 ` Ben Munat
2005-09-06  6:08   ` ysharma
2005-09-06 16:41     ` Ben Munat
2005-09-06 21:53       ` [gentoo-server] prioritising security updates Jeremy Brake
2005-09-06 22:14         ` Paul Kölle
2005-09-07  6:12         ` Michael Irey
2005-09-07  6:48           ` W.Kenworthy
2005-09-07 15:28             ` Matthias Bethke
2005-09-07 22:56               ` William Kenworthy
2005-09-08 12:19                 ` Matthias Bethke
2005-09-07 12:21         ` xyon
2005-09-08 14:39         ` A. Khattri

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=431F1381.7020505@munat.com \
    --to=bent@munat.com \
    --cc=gentoo-server@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