Re: [gentoo-user] ruby 22

[Alec Ten Harmsel]

TL;DR: re-sync and you should be fine.


On 08/20/2017 12:36 PM, allan gottlieb wrote:


Not sure I understand.

1.  I should have been more complete about the command I run
   
   MAKEOPTS="--jobs=8 --load-average=5"

   emerge --ask --deep --tree --jobs --load-average=5 \
  --update --changed-use --with-bdeps=y @world

2.  I do not have "ruby" or "RUBY" anywhere in the tree rooted
 at /etc/portage


Cool, that makes it easier.



3.  emerge did not offer to upgrade RUBY_TARGETS does
 not seem happy with ruby21 since the emerge output includes
 [ebuild   R]dev-ruby/test-unit-3.1.9  RUBY_TARGETS="(-ruby21%*)"
 [ebuild   R]dev-ruby/rdoc-4.2.0  RUBY_TARGETS="(-ruby21%*)"
 [ebuild   R]dev-ruby/minitest-5.8.4  RUBY_TARGETS="(-ruby21%*)"


RUBY_TARGETS is set in the profiles that are part of the portage tree.



4.  I synced the tree today just before the emerge.  Might I have picked
 up an inconsistent tree and hence should I resync?


Hans de Graaff replied a bit ago; it looks like RUBY_TARGETS in the 
profiles were not updated after ruby-2.1 was masked. If you re-sync, you 
should be able to go forward with the update.






6.  I have NOT done the eselect ruby set ruby 22.

As Hans also mentioned, the upgrade itself will not automatically run 
the eselect command - my bad. Once you do a depclean and ruby-2.1 is 
removed, eselect will be run to set the system ruby version to 2.2.


Alec

Re: [gentoo-user] ruby 22

[Stroller]

> On 20 Aug 2017, at 15:19, 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

If this was a mistake on your part then you're not alone.

I appear currently to have both ruby-2.1.9 and ruby-2.2.6 installed on two 
systems, last sync'd 6/7/2017 and 20/7/2017, with select showing ruby21 as 
current version on both.

Stroller.

Re: [gentoo-user] ruby 22

[allan gottlieb]

On Sun, Aug 20 2017, Alec Ten Harmsel wrote:

> 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

Not sure I understand.

1.  I should have been more complete about the command I run
  
  MAKEOPTS="--jobs=8 --load-average=5"
  emerge --ask --deep --tree --jobs --load-average=5 \
 --update --changed-use --with-bdeps=y @world

2.  I do not have "ruby" or "RUBY" anywhere in the tree rooted
at /etc/portage

3.  emerge did not offer to upgrade RUBY_TARGETS does
not seem happy with ruby21 since the emerge output includes
[ebuild   R]dev-ruby/test-unit-3.1.9  RUBY_TARGETS="(-ruby21%*)" 
[ebuild   R]dev-ruby/rdoc-4.2.0  RUBY_TARGETS="(-ruby21%*)" 
[ebuild   R]dev-ruby/minitest-5.8.4  RUBY_TARGETS="(-ruby21%*)" 

4.  I synced the tree today just before the emerge.  Might I have picked
up an inconsistent tree and hence should I resync?

5.  The emerge error msg is below.

6.  I have NOT done the eselect ruby set ruby 22.

Thanks for you help
allan



>>> Install rdoc-4.2.0 into /var/tmp/portage/dev-ruby/rdoc-4.2.0/image/ 
>>> category dev-ruby
 * Running install phase for ruby22 ...
 * Running install phase for all ...
 * ERROR: dev-ruby/rdoc-4.2.0::gentoo failed (install phase):
 *   USE Flag 'ruby_targets_ruby21' not in IUSE for dev-ruby/rdoc-4.2.0
 * 
 * Call stack:
 *  ebuild.sh, line  115:  Called src_install
 *environment, line 4405:  Called ruby-ng_src_install
 *environment, line 4105:  Called _ruby_invoke_environment 'all' 
'all_ruby_install'
 *environment, line  540:  Called all_ruby_install
 *environment, line  636:  Called use 'ruby_targets_ruby21'
 *   phase-helpers.sh, line  200:  Called die
 * The specific snippet of code:
 *  die "USE Flag '${u}' not in IUSE for 
${CATEGORY}/${PF}"
 * 
 * If you need support, post the output of `emerge --info 
'=dev-ruby/rdoc-4.2.0::gentoo'`,
 * the complete build log and the output of `emerge -pqv 
'=dev-ruby/rdoc-4.2.0::gentoo'`.

Re: [gentoo-user] ruby 22

[Alec Ten Harmsel]

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

[gentoo-user] ruby 22

[allan gottlieb]

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?

Thanks,
allan