From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] emerge --depclean question
Date: Sat, 30 Dec 2006 17:51:29 -0800 [thread overview]
Message-ID: <5bdc1c8b0612301751k5f65c464nf8b9bd99c3b75091@mail.gmail.com> (raw)
Hi,
I haven't done this in quite awhile so this evening I started
looking at dependencies a bit. I thought I might take a shot at
cleaning things up old stuff left around from updates over the last
year or so. I ran emerge -p --depclean and was told that there were
about 45 things to remove so I decided I'd try removing a few
one-at-a-time and see how it went. First I sync'ed and did an emerge
-DuN world and made sure the machine was up to date. I then removed
what seemed like a pretty random entry late on the list - imlib - and
then a revdep-rebuild -p to see what it thought. I was then told I
needed to emerge revisions of two new things - gnome-lib and
gtk-pixbuf - neither of which existed according to both emerge and
eix. I then re-emerged imlib, reran revdep-rebuild and now I see the
machine is consistent again.
What's up with that?
I then tried again with something called 'jasper'. Rerunning
revdep-rebuild is now telling me it needs to reemerge netpbm and this
will pick up jasper again. I did that emerge and reran revdep-rebuild
again and the machine is once again clean.
What's up with that?
Is this a question that certain ebuilds are not written correctly
and don't somehow call for the right dependencies, or is it something
else?
Also, is there any better tool these days for cleaning up stale
packages left around than emerge --depclean?
Thanks,
Mark
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2006-12-31 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 1:51 Mark Knecht [this message]
2006-12-31 13:11 ` [gentoo-amd64] Re: emerge --depclean question Duncan
2006-12-31 15:09 ` Mark Knecht
2006-12-31 18:48 ` Mark Knecht
2006-12-31 22:04 ` Marek Wróbel
2006-12-31 23:15 ` Mark Knecht
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=5bdc1c8b0612301751k5f65c464nf8b9bd99c3b75091@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@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