| 1 |
TL;DR: re-sync and you should be fine. |
| 2 |
|
| 3 |
|
| 4 |
On 08/20/2017 12:36 PM, allan gottlieb wrote: |
| 5 |
> |
| 6 |
> Not sure I understand. |
| 7 |
> |
| 8 |
> 1. I should have been more complete about the command I run |
| 9 |
> |
| 10 |
> MAKEOPTS="--jobs=8 --load-average=5" |
| 11 |
> emerge --ask --deep --tree --jobs --load-average=5 \ |
| 12 |
> --update --changed-use --with-bdeps=y @world |
| 13 |
> |
| 14 |
> 2. I do not have "ruby" or "RUBY" anywhere in the tree rooted |
| 15 |
> at /etc/portage |
| 16 |
|
| 17 |
Cool, that makes it easier. |
| 18 |
|
| 19 |
> |
| 20 |
> 3. emerge did not offer to upgrade RUBY_TARGETS does |
| 21 |
> not seem happy with ruby21 since the emerge output includes |
| 22 |
> [ebuild R ] dev-ruby/test-unit-3.1.9 RUBY_TARGETS="(-ruby21%*)" |
| 23 |
> [ebuild R ] dev-ruby/rdoc-4.2.0 RUBY_TARGETS="(-ruby21%*)" |
| 24 |
> [ebuild R ] dev-ruby/minitest-5.8.4 RUBY_TARGETS="(-ruby21%*)" |
| 25 |
|
| 26 |
RUBY_TARGETS is set in the profiles that are part of the portage tree. |
| 27 |
|
| 28 |
> |
| 29 |
> 4. I synced the tree today just before the emerge. Might I have picked |
| 30 |
> up an inconsistent tree and hence should I resync? |
| 31 |
|
| 32 |
Hans de Graaff replied a bit ago; it looks like RUBY_TARGETS in the |
| 33 |
profiles were not updated after ruby-2.1 was masked. If you re-sync, you |
| 34 |
should be able to go forward with the update. |
| 35 |
|
| 36 |
> |
| 37 |
> |
| 38 |
> |
| 39 |
> 6. I have NOT done the eselect ruby set ruby 22. |
| 40 |
> |
| 41 |
As Hans also mentioned, the upgrade itself will not automatically run |
| 42 |
the eselect command - my bad. Once you do a depclean and ruby-2.1 is |
| 43 |
removed, eselect will be run to set the system ruby version to 2.2. |
| 44 |
|
| 45 |
Alec |
Archives