[gentoo-user] Stray dependency on virtual/x11-7.0-r2

[gentoo-user] Stray dependency on virtual/x11-7.0-r2

[Kevin O'Gorman]

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?

++ kevin


-- 
Kevin O'Gorman, PhD
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Stray dependency on virtual/x11-7.0-r2

[Greg Bur]

[-- 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 --]

Re: [gentoo-user] Stray dependency on virtual/x11-7.0-r2

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

On Sunday 17 September 2006 08:18, Kevin O'Gorman 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

I have to say that I am a bit curious as to which package would require you to 
install virtual/x11. Please add --tree to `emerge -aDvu world` and show what 
pulls this in.

virtual/x11 is a virtual package which means it depends on a number of other 
packages but provides nothing other than it's dependencies...

> The migration guide says this can happen when there's an outdated package.

Sounds about right...

> But equery says there are well over 100 such packages that depend on
> virtual/x11.

As has been said before on this list equery is broken and unreliable. Last I 
checked it had 44 open bugs against it. When a 100 packages show up for 
`equery depends virtual/x11` it means that 100 packages have a dependency 
that could be satisfied by virtual/x11. That's quite different from 100 
packages depend on virtual/x11. In most if not all of those cases one or 
several other packages would be able to satisfy the same dependency hence 
virtual/x11 isn't actually required at all (at least on my system it isn't):

$ eix -e x11
* virtual/x11
     Available versions:  6.8 7.0-r2
     Installed:           none
     Homepage:            http://www.gentoo.org/proj/en/desktop/x/x11/
     Description:         Virtual for the core X11 implementation

$ equery depends virtual/x11 | wc -l
387

$ emerge -uvpD world

These are the packages that would be merged, in order:

Calculating world dependencies... done!

Total size of downloads: 0 kB

> 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?

Nope.

> 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.

Of course.

[SNIP]
Can I get away with just waiting for a while?

Sure.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Stray dependency on virtual/x11-7.0-r2

[Kevin O'Gorman]

On 9/17/06, Greg Bur <greg.bur@gmail.com> wrote:
> 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

Thanks.  That was very helpful.  The --tree showed that there was only one
culprit package, and I don't need it.  Bye, bye, problem.

++ kevin

-- 
Kevin O'Gorman, PhD
-- 
gentoo-user@gentoo.org mailing list