On 9/17/06, <b class="gmail_sendername">Kevin O'Gorman</b> &lt;<a href="mailto:kogorman@gmail.com">kogorman@gmail.com</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I just switched to modular X, and got to the point where the system<br>comes up okay.<br>I have a few remaining puzzles and problems.&nbsp;&nbsp;Here's one:<br><br>When I do emerge -aDvu world, it wants to emerge<br>[ebuild&nbsp;&nbsp;N&nbsp;&nbsp;&nbsp;&nbsp;] virtual/x11-
7.0-r2&nbsp;&nbsp;USE=&quot;dri&quot; 0 kB<br><br>The migration guide says this can happen when there's an outdated package.<br>But equery says there are well over 100 such packages that depend on<br>virtual/x11.&nbsp;&nbsp;And they're all up to date.&nbsp;&nbsp;I've been running stable so far, with
<br>very few exceptions.&nbsp;&nbsp;Am I really to go unstable with all of these?&nbsp;&nbsp;This seems<br>extreme in view of the fact that a great many of them are KDE things, but<br>KDE seems to be working just fine.<br><br>What's a guy to do?&nbsp;&nbsp;Can I get away with just waiting for a while?
</blockquote><div><br><br>emerge -aDvut will show the dependency tree which should tell you which package requires virtual/x11-7.0-r2.&nbsp; Once you have narrowed down which package requires it to be installed you can deal with it from there.&nbsp; Instead of going unstable with your entire system you can add the offending package to /etc/portage/package.keywords for instance.&nbsp; If it's a package you know you don't need you could also remove it.&nbsp; HTH
<br><br>Regards,<br><br>Greg<br></div><br></div><br>