Hi! In the mentioned ebuild the following lines in RDEPEND !<x11-base/xorg-x11-6.8.0-r4 !<media-video/ati-drivers-8.8.25-r3 are better changed to >=x11-base/xorg-x11-6.8.0-r4 >=media-video/ati-drivers-8.8.25-r3 (Not lower than is equivalent to greater than or equal - not quite a mathematical mystery... ;o) Portage obviously doesn't support the cumbersome logic and reports that the respective packages are blocked by opengl-update. Regards, Torsten Reproducible: Always Steps to Reproduce: 1. 2. 3.
That would create a circular dependency in the case of xorg-x11, which is a no-no. new xorg depends on >=opengl-update-1.99, so for opengl-update-2 to depend on new xorg would make it impossible to get either of them when starting with neither. The "answer" to this is blocking lower versions, which allows the circle to work with a little annoyance -- uninstalling xorg before upgrading to the new one. Although this isn't perfect, it's better than the alternative of allowing a broken combination of new opengl-update and old xorg. In the ati-drivers case, it's not a dependency, it's something that can't be simultaneously installed with new opengl-update. Thus changing it to >= would actually be wrong. So in this case, '!<' != '>='. In summary, the first one is impossible because of a circular dependency and the second is incorrect. CC'ing committer so he can see the discussion.
Here is a nicer workaround: first emerge --nodeps xorg-x11 and then emerge -uD world works for me. Christoph
You should be able to update xorg-x11 to -r4 or .901 using opengl-update-2.0_pre*, but 2.1 relies on the X11 libs being installed in /usr/lib{,32,64} rather than /usr/X11R6/lib{,32,64}
After updating to Xorg-6.8.1.xxx one half of the problem is gone, the other persists: It should really be >=media-video/ati-drivers-8.8.25-r3 since media-video/ati-drivers-8.8.25-r3 insists on >=opengl-update-2.1_pre1 Thus, with !<media-video/ati-drivers-8.8.25-r3 the whole thing becomes mutually exclusive and blocks portage! Would be nice, if someone could have a look into that again! TIA, Torsten
Torsten: Yes, it should work fine if you do emerge -v ati-drivers && emerge -uvD world
Are the portage developers aware of this circluar dependancy problem? This really something portage should be able to take care of.
Yes, they are aware of the problem, but due to lack of developer resources and interest, it is not a high priority...
Is there a bug for emerge not handling situation like this and bug 85519? If not, should there be?
dupe of #79606
*** This bug has been marked as a duplicate of 79606 ***