| 1 |
On Sun, Aug 20 2017, Alec Ten Harmsel wrote: |
| 2 |
|
| 3 |
> On 08/20/2017 08:19 AM, allan gottlieb wrote: |
| 4 |
>> I am currently running ruby21 (ruby-2.1.9). |
| 5 |
>> All such versions of ruby are masked so this is clearly a mistake |
| 6 |
>> on my part. I was alerted to this error by dev-ruby/rdoc-4.2.0 |
| 7 |
>> failing to build on today's emerge --update @world |
| 8 |
>> |
| 9 |
>> After I do |
| 10 |
>> eselect ruby set ruby22 |
| 11 |
>> can I simply |
| 12 |
>> emerge --update @world |
| 13 |
>> or must I explicitly rebuild some ruby packages? |
| 14 |
> |
| 15 |
> I don't believe that will be enough. You should update RUBY_TARGETS in |
| 16 |
> /etc/portage/make.conf if you have it set. If you don't have it set |
| 17 |
> and are still getting this error, that's a bug and should be filed on |
| 18 |
> b.g.o. I have a custom RUBY_TARGETS as I do some ruby development, so |
| 19 |
> I don't have a vanilla system to test this on. |
| 20 |
> |
| 21 |
> Also, you'll have to run a slightly different command to update (since |
| 22 |
> RUBY_TARGETS, PYTHON_TARGETS, etc. are USE flags underneath): |
| 23 |
> |
| 24 |
> emerge --update --newuse --deep @world |
| 25 |
> |
| 26 |
> You shouldn't have to 'eselect ruby' either - portage will do this for |
| 27 |
> you while updating. |
| 28 |
> |
| 29 |
> Alec |
| 30 |
|
| 31 |
Not sure I understand. |
| 32 |
|
| 33 |
1. I should have been more complete about the command I run |
| 34 |
|
| 35 |
MAKEOPTS="--jobs=8 --load-average=5" |
| 36 |
emerge --ask --deep --tree --jobs --load-average=5 \ |
| 37 |
--update --changed-use --with-bdeps=y @world |
| 38 |
|
| 39 |
2. I do not have "ruby" or "RUBY" anywhere in the tree rooted |
| 40 |
at /etc/portage |
| 41 |
|
| 42 |
3. emerge did not offer to upgrade RUBY_TARGETS does |
| 43 |
not seem happy with ruby21 since the emerge output includes |
| 44 |
[ebuild R ] dev-ruby/test-unit-3.1.9 RUBY_TARGETS="(-ruby21%*)" |
| 45 |
[ebuild R ] dev-ruby/rdoc-4.2.0 RUBY_TARGETS="(-ruby21%*)" |
| 46 |
[ebuild R ] dev-ruby/minitest-5.8.4 RUBY_TARGETS="(-ruby21%*)" |
| 47 |
|
| 48 |
4. I synced the tree today just before the emerge. Might I have picked |
| 49 |
up an inconsistent tree and hence should I resync? |
| 50 |
|
| 51 |
5. The emerge error msg is below. |
| 52 |
|
| 53 |
6. I have NOT done the eselect ruby set ruby 22. |
| 54 |
|
| 55 |
Thanks for you help |
| 56 |
allan |
| 57 |
|
| 58 |
================================================================ |
| 59 |
|
| 60 |
>>> Install rdoc-4.2.0 into /var/tmp/portage/dev-ruby/rdoc-4.2.0/image/ category dev-ruby |
| 61 |
* Running install phase for ruby22 ... |
| 62 |
* Running install phase for all ... |
| 63 |
* ERROR: dev-ruby/rdoc-4.2.0::gentoo failed (install phase): |
| 64 |
* USE Flag 'ruby_targets_ruby21' not in IUSE for dev-ruby/rdoc-4.2.0 |
| 65 |
* |
| 66 |
* Call stack: |
| 67 |
* ebuild.sh, line 115: Called src_install |
| 68 |
* environment, line 4405: Called ruby-ng_src_install |
| 69 |
* environment, line 4105: Called _ruby_invoke_environment 'all' 'all_ruby_install' |
| 70 |
* environment, line 540: Called all_ruby_install |
| 71 |
* environment, line 636: Called use 'ruby_targets_ruby21' |
| 72 |
* phase-helpers.sh, line 200: Called die |
| 73 |
* The specific snippet of code: |
| 74 |
* die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}" |
| 75 |
* |
| 76 |
* If you need support, post the output of `emerge --info '=dev-ruby/rdoc-4.2.0::gentoo'`, |
| 77 |
* the complete build log and the output of `emerge -pqv '=dev-ruby/rdoc-4.2.0::gentoo'`. |
Archives