| 1 |
On Sun, Sep 1, 2013 at 7:43 PM, Rick "Zero_Chaos" Farina |
| 2 |
<zerochaos@g.o> wrote: |
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA1 |
| 5 |
> |
| 6 |
>> ozzie src # emerge -vp ruby |
| 7 |
>> |
| 8 |
>> |
| 9 |
>> These are the packages that would be merged, in reverse order: |
| 10 |
>> |
| 11 |
>> Calculating dependencies... done! |
| 12 |
>> |
| 13 |
>> emerge: there are no ebuilds built with USE flags to satisfy |
| 14 |
>> ">=dev-ruby/rake-0.9.6[ruby_targets_ruby20]". !!! One of the |
| 15 |
>> following packages is required to complete your request: - |
| 16 |
>> dev-ruby/rake-0.9.6::gentoo (Change USE: +ruby_targets_ruby20) |
| 17 |
>> (dependency required by "dev-lang/ruby-2.0.0_p247-r1" [ebuild]) |
| 18 |
>> (dependency required by "ruby" [argument]) |
| 19 |
> |
| 20 |
> |
| 21 |
> So, um, why exactly is ruby 2.0.0 stable if I can't even update my |
| 22 |
> system anymore? I'm having the same issue across 3 systems so I'm |
| 23 |
> assuming it's not a bad sync. |
| 24 |
> |
| 25 |
> Whatever the current "solution" to not adding ruby20 to RUBY_TARGETS |
| 26 |
> is, it's not work for me. |
| 27 |
> |
| 28 |
> - -Zero |
| 29 |
|
| 30 |
My best guess is that there is some package in your world depgraph |
| 31 |
which is pulling in dev-lang/ruby via an unbounded (unslotted) |
| 32 |
dependency. This causes portage to try to upgrade to ruby-2.0 |
| 33 |
automatically, which fails when you don't have ruby20 in RUBY_TARGETS. |
| 34 |
|
| 35 |
equery depends seems to show that there are quite a few packages with |
| 36 |
such dependencies in the tree. |
| 37 |
|
| 38 |
Ruby team: Is there something we are missing that would somehow avoid |
| 39 |
this problem? It is bound to generate some confusion among users. |
Archives