On my last sync, which I performed twice to make sure it wasn't a sync error or the sync missed something, portage has some Gnome ebuilds that call for a version of ruby-libart2 that does not exist in portage. Whoever wrote these ebuilds should check into this, or the portage maintainers should include the required version of ruby-libart2 in the portage tree. Reproducible: Always Steps to Reproduce: 1. emerge --sync (as of 16 July) 2. emerge -pvuDN world, or emerge -pv ruby-gnome2 if you don't have a Gnome DE set up Actual Results: Output should be this or something similar: These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy ">=dev-ruby/ruby-libart2-0.19.0". (dependency required by "dev-ruby/ruby-gnomecanvas2-0.19.0" [ebuild]) (dependency required by "dev-ruby/ruby-gnome2-0.19.0" [ebuild]) (dependency required by "gnome-extra/gnome-art-0.2-r2" [installed]) (dependency required by "@world" [argument]) Expected Results: Smooth world update or emerge of individual packages without asking for a dependency version that is not in the tree.
*** This bug has been marked as a duplicate of bug 278061 ***