I don't know why this happens, but always when I do an emerge -puvD world, portage wants to install lablgtk-2.2.0 (and several other packages lablgtk-2 needs). I tracked it down to mldonkey, that is the only program on my system that needs lablgtk (which is not in my world). The ebuild says RDEPEND="gtk? ( >=dev-ml/lablgtk-1.2.6 <dev-ml/lablgtk-2 ) which I would read as "install 1.2.6 or newer, but not a 2.x version". However, if I unmerge lablgtk (mldonkey is still installed) and afterwards do "emerge -poD net-p2p/mldonkey", it wants to install BOTH, 1.2.6 and 2.2.0. This might be a bug in portage, however if i change the line to RDEPEND="gtk? ( =dev-ml/lablgtk-1.2.6 ) everything works fine. The old version of this ebuild hat the line RDEPEND="gtk? ( =dev-ml/lablgtk-1* ) instead, which also worked as expected. Reproducible: Always Steps to Reproduce:
fixed in portage; sorry about that, newer mldonkeys rely on >=lablgtk-1.2.6 but not lablgtk-2*, while older ones could have used earlier 1.2* versions.
