We cannot update dbus to version 1.0.2 because line 20 of dbus-1.0.2.ebuild (!<sys-apps/dbus-0.91) blocks it. We have first to uninstall our actual version.
Steev Klimaszewski is the author of this change. I could not reach him to put me clear on the reasons he had.
Having this block means that dbus is not properly upgraded on an emerge --update world.
When doing "emerge --update --deep world," portage tries to install both dbus-1.0.2 and dbus-0.91 (I don't have either of those installed). Because dbus-0.91 blocks dbus-1.0.2, however, I cannot do an "emerge --update --deep world."
(In reply to comment #1)
> When doing "emerge --update --deep world," portage tries to install both
> dbus-1.0.2 and dbus-0.91
No it doesn't, there's no dbus-0.91 ebuild. Plus see Bug 1343.
Jakub: With all respect, Comment #1 was not the point of this bug. Actually, you just have made a point out of your Comment #2. Seemingly, Steeve wanted the dep to be available due to testing. Now there are not 0.90 test ebuilds anymore.
Then the bug request becomes: Please remove <dbus-0.91 line because the test phase has been completed and the 0.90 ebuilds were removed from the Portage tree.
Thanks in advance.
No, it is in there because you CANNOT have dbus < .90 installed when you attempt to install 1.0.x - Please see the bug that Jakub linked for the reason why.