Ok, so I get the output below when trying to merge after a sync today. My guess is that the openmotif package was made into two separate packages, correct?
To the portage developers, how could this be handled? Perhaps emerge could somehow figure out the reason for such a conflict, and then automatically unmerge the original package? The fix for this was to "emerge --unmerge openmotif", and then re-emerge it. Then I was finally able to do a system update. Do you want this reported as a bug, or is it already? [00:16 [EMAIL PROTECTED] data] # emerge --ask --update --deep --newuse --buildpkg world These are the packages that I would merge, in order: Calculating world dependencies ...done! [blocks B ] =x11-libs/openmotif-2.2.3-r3 (is blocking x11-libs/motif-config-0.9) [ebuild U ] sys-devel/gcc-config-1.3.12-r5 [1.3.12-r4] [ebuild U ] sys-apps/man-pages-2.18 [2.16] [ebuild N ] x11-libs/cairo-1.0.2 [ebuild U ] dev-libs/glib-2.8.4 [2.6.5] [ebuild U ] dev-libs/atk-1.10.3 [1.10.1] [ebuild U ] x11-libs/pango-1.10.2 [1.8.1-r1] [ebuild U ] x11-libs/gtk+-2.8.8 [2.6.10-r1] [ebuild U ] dev-libs/libgcrypt-1.2.2-r1 [1.2.1] [ebuild U ] sys-apps/module-init-tools-3.2.1 [3.0-r2] [ebuild U ] net-analyzer/ethereal-0.10.14 [0.10.13-r2] [ebuild N ] x11-libs/motif-config-0.9 [ebuild U ] x11-libs/openmotif-2.2.3-r8 [2.2.3-r3] [ebuild U ] media-sound/alsa-headers-1.0.10 [1.0.10_rc3] [ebuild U ] media-libs/alsa-lib-1.0.10 [1.0.10_rc3] [ebuild U ] kde-base/kpdf-3.4.3-r3 [3.4.3-r2] [ebuild U ] sys-apps/findutils-4.1.20-r2 [4.1.20-r1] [ebuild N ] virtual/libstdc++-3.3 [ebuild U ] app-portage/gentoolkit-0.2.2_pre1 [0.2.1_rc3] !!! Error: The above package list contains packages which cannot be installed !!! on the same system. -- gentoo-user@gentoo.org mailing list