From: "Daiajo Tibdixious" <daiajo@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] revdep-rebuild rebuilding nonsense
Date: Thu, 1 Feb 2007 10:20:12 +1100 [thread overview]
Message-ID: <a4a9bfcb0701311520g1f16f813vb05f416f9bfe0c7d@mail.gmail.com> (raw)
In-Reply-To: <200701312356.36611.clip2@gmx.de>
On 2/1/07, Dieter Ries <clip2@gmx.de> wrote:
> on my gentoo server box i did an emerge --depclean and revdep-rebuild
> afterwards, but now, revdep rebuild gives me the following output:
Just when thru this myself.
> emerge --oneshot =gnome-base/gnome-libs-1.4.2 =kde-base/kdepim-3.5.5-r2
> =media-gfx/gimp-2.2.12 =media-gfx/imagemagick-6.3.0.5
> =media-libs/gdk-pixbuf-0.22.0-r5 =media-video/mplayer-1.0_rc1
> =x11-libs/wxGTK-2.6.2-r1
The important part is the "broken blah (requires blah blah blah)" lines.
> emerge: there are no ebuilds to satisfy "=gnome-base/gnome-libs-1.4.2".
> so why would revdep-rebuild emerge ebuilds which don't exist???
It's stupid. :) Its great at detecting broken linkage, lousy at fixing
it. I NEVER allow revdep-rebuild to rebuild ANYTHING. If I think the
"broken ..." actually match the list of packages, I'll emerge them
manually with --update.
Much less hassle that way.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-31 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 22:56 [gentoo-amd64] revdep-rebuild rebuilding nonsense Dieter Ries
2007-01-31 23:06 ` [gentoo-amd64] " Harm Geerts
2007-02-01 2:58 ` Daniel Gryniewicz
2007-02-01 10:33 ` Neil Bothwick
2007-01-31 23:17 ` [gentoo-amd64] " Bo Ørsted Andresen
2007-01-31 23:24 ` Dieter Ries
2007-01-31 23:20 ` Daiajo Tibdixious [this message]
2007-01-31 23:21 ` Daiajo Tibdixious
2007-01-31 23:35 ` Bo Ørsted Andresen
2007-01-31 23:58 ` Daiajo Tibdixious
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=a4a9bfcb0701311520g1f16f813vb05f416f9bfe0c7d@mail.gmail.com \
--to=daiajo@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