Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Hi, Portage has an error in building the subdependency list for bigger packets. I ran into following : stuga3 glu # emerge -p openmotif These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] x11-misc/xbitmaps-1.0.1 USE="-debug" [ebuild N ] x11-libs/openmotif-2.2.3-r9 This is correct so far, but if I try to emerge xorg-x11 : stuga3 X11 # emerge -p xorg-x11 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] x11-libs/openmotif-2.2.3-r9 I think this is a major bug, cause it breaks compiles. Greetings Janosch
Please attach --debug ouput for the command that produces undesirable results.
Hi, actually what I said before wasn't accurate enought... The dependency list itself ist build correct, but the ordering is wrong : stuga3 glu # emerge -p xorg-x11 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] x11-libs/openmotif-2.2.3-r9 ... [ebuild N ] x11-misc/xbitmaps-1.0.1 USE="-debug" And here some system info : stuga3 glu # emerge --version Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.9-gentoo-r6 i686)
Created an attachment (id=90227) [details] debug output of emerge xorg-x11 with --debug
Created an attachment (id=90228) [details] output of emerge openmotif with --debug
Just for you I unmerged the packages again ;-), it is still reproducable... (emergeing xbitmaps with --oneshot did the trick...)
The problem is that the openmotif dep on xbitmaps is of the form || ( ( modular deps ) virtual/x11 ). It's a known issue that the resolver isn't currently able to handle this correctly. I've recommended to use <virtual/x11-7 instead of virtual-x11 but nobody seems to be taking that recommendation.
This is certainly a shorcomming of the resolver, but || ( ( modular deps ) <virtual/x11-7 ) would be a simple solution for the time being... *** This bug has been marked as a duplicate of 133671 ***