On Sun, Sep 1, 2013 at 7:43 PM, Rick "Zero_Chaos" Farina <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> ozzie src # emerge -vp ruby >> >> >> These are the packages that would be merged, in reverse order: >> >> Calculating dependencies... done! >> >> emerge: there are no ebuilds built with USE flags to satisfy >> ">=dev-ruby/rake-0.9.6[ruby_targets_ruby20]". !!! One of the >> following packages is required to complete your request: - >> dev-ruby/rake-0.9.6::gentoo (Change USE: +ruby_targets_ruby20) >> (dependency required by "dev-lang/ruby-2.0.0_p247-r1" [ebuild]) >> (dependency required by "ruby" [argument]) > > > So, um, why exactly is ruby 2.0.0 stable if I can't even update my > system anymore? I'm having the same issue across 3 systems so I'm > assuming it's not a bad sync. > > Whatever the current "solution" to not adding ruby20 to RUBY_TARGETS > is, it's not work for me. > > - -Zero
My best guess is that there is some package in your world depgraph which is pulling in dev-lang/ruby via an unbounded (unslotted) dependency. This causes portage to try to upgrade to ruby-2.0 automatically, which fails when you don't have ruby20 in RUBY_TARGETS. equery depends seems to show that there are quite a few packages with such dependencies in the tree. Ruby team: Is there something we are missing that would somehow avoid this problem? It is bound to generate some confusion among users.
