On 08/20/2017 08:19 AM, allan gottlieb wrote:
I am currently running ruby21 (ruby-2.1.9).
All such versions of ruby are masked so this is clearly a mistake
on my part. I was alerted to this error by dev-ruby/rdoc-4.2.0
failing to build on today's emerge --update @world
After I do
eselect ruby set ruby22
can I simply
emerge --update @world
or must I explicitly rebuild some ruby packages?
I don't believe that will be enough. You should update RUBY_TARGETS in
/etc/portage/make.conf if you have it set. If you don't have it set and
are still getting this error, that's a bug and should be filed on b.g.o.
I have a custom RUBY_TARGETS as I do some ruby development, so I don't
have a vanilla system to test this on.
Also, you'll have to run a slightly different command to update (since
RUBY_TARGETS, PYTHON_TARGETS, etc. are USE flags underneath):
emerge --update --newuse --deep @world
You shouldn't have to 'eselect ruby' either - portage will do this for
you while updating.
Alec
