hi, what's wrong here? # emerge opera -pv These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] x11-libs/openmotif-2.1.30-r4 0 kB [ebuild N ] media-libs/lcms-1.12 +jpeg +python -tiff +zlib 554 kB [ebuild N ] media-libs/libmng-1.0.4 555 kB [ebuild N ] media-libs/libungif-4.1.0.1b +X +gif 305 kB [ebuild N ] gnome-base/ORBit-0.5.17 +nls 0 kB [ebuild N ] gnome-base/gnome-libs-1.4.2 -doc -kde +nls 2,807 kB [ebuild N ] dev-db/unixODBC-2.2.6 +gnome +qt 2,128 kB [ebuild N ] x11-libs/qt-3.3.0-r1 +cups -doc -firebird +gif -icc -ipv6 -mysql -nas +odbc +opengl -postgres -sqlite -xinerama +zlib 14,064 kB [ebuild N ] net-www/opera-7.23-r1 -operanom2 -static 24,647 kB Total size of downloads: 45,063 kB well, unixODBC gets emerged before qt, but unixODBC depends on qt. In addition portage sometimes tries to emerge both blackdown-jre and blackdown-jdk but blackdown-jdk is a superset of backdown-jre and it seems to me, that portage doesn't include everything that the ebuild provides. Reproducible: Always Steps to Reproduce: 1. 2. 3.
well, forget my last comment about blackdown-jdk and blackdown-jre. it's very hard for portage to resolv that, since the portage might first find a dependency on virtual/jre and therefor selects blackdown-jre. if it than finds a dependency on virtual/jdk, portage will decide to emerge blackdown-jdk. to overcome the problem, portage may perform a cleanup of the package-list by removing a package if another package exists, that is a superset, but that might take some time.
Can you show us 'emerge info' and 'emerge opera -pvt' too?
*** This bug has been marked as a duplicate of 14178 ***
