| 1 |
On Sun, Feb 14, 2021 at 02:41:31PM -0500, John Covici wrote: |
| 2 |
> Hi. In trying to do my world update today, I have run into some kind |
| 3 |
> of ruby problem. |
| 4 |
> |
| 5 |
> When doing the update portage had me add changes, seems mostly to do |
| 6 |
> with add ruby 3.0 as a ruby_target. Now, I get the following at the |
| 7 |
> end of my world update log |
| 8 |
[...] |
| 9 |
> 1: from /usr/lib64/ruby/2.5.0/rubygems.rb:17:in `<top (required)>' |
| 10 |
|
| 11 |
Unlike python, ruby is not very good at selecting a version that works |
| 12 |
so eselect ruby actually matters. Here it's trying to 2.5.0 while it's |
| 13 |
half uninstalled and unsurprisingly fail. |
| 14 |
|
| 15 |
Have a look at "eselect ruby list" and set a version that's actually in |
| 16 |
RUBY_TARGETS |
| 17 |
|
| 18 |
With profile's default that'd be "eselect ruby set ruby26" or 30 if |
| 19 |
that's what you're using now. |
| 20 |
|
| 21 |
-- |
| 22 |
ionen |
Archives