From: "Greg Bur" <greg.bur@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Stray dependency on virtual/x11-7.0-r2
Date: Sun, 17 Sep 2006 03:17:28 -0400 [thread overview]
Message-ID: <976cb44f0609170017v26716edan756af0cd3bf987ea@mail.gmail.com> (raw)
In-Reply-To: <9acccfe50609162318k3563171fib797ef39fc195998@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
On 9/17/06, Kevin O'Gorman <kogorman@gmail.com> wrote:
>
> I just switched to modular X, and got to the point where the system
> comes up okay.
> I have a few remaining puzzles and problems. Here's one:
>
> When I do emerge -aDvu world, it wants to emerge
> [ebuild N ] virtual/x11-7.0-r2 USE="dri" 0 kB
>
> The migration guide says this can happen when there's an outdated package.
> But equery says there are well over 100 such packages that depend on
> virtual/x11. And they're all up to date. I've been running stable so
> far, with
> very few exceptions. Am I really to go unstable with all of these? This
> seems
> extreme in view of the fact that a great many of them are KDE things, but
> KDE seems to be working just fine.
>
> What's a guy to do? Can I get away with just waiting for a while?
emerge -aDvut will show the dependency tree which should tell you which
package requires virtual/x11-7.0-r2. Once you have narrowed down which
package requires it to be installed you can deal with it from there.
Instead of going unstable with your entire system you can add the offending
package to /etc/portage/package.keywords for instance. If it's a package
you know you don't need you could also remove it. HTH
Regards,
Greg
[-- Attachment #2: Type: text/html, Size: 1697 bytes --]
next prev parent reply other threads:[~2006-09-17 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 6:18 [gentoo-user] Stray dependency on virtual/x11-7.0-r2 Kevin O'Gorman
2006-09-17 7:17 ` Greg Bur [this message]
2006-09-17 18:20 ` Kevin O'Gorman
2006-09-17 13:23 ` Bo Ørsted Andresen
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=976cb44f0609170017v26716edan756af0cd3bf987ea@mail.gmail.com \
--to=greg.bur@gmail.com \
--cc=gentoo-user@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