On Tue, Aug 22, 2017 at 07:57:39AM -0400, John Covici wrote: > > > > I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the > > default, but when I ran emerge --depclean I still have packages > > pulling ruby21 as follows: > > > > Calculating dependencies .. ..... done! > > dev-lang/ruby-2.1.10 pulled in by: > > dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1 > > dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1 > > dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1 > > dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1 > > dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1 > > dev-ruby/minitest-5.10.3 requires > > dev-lang/ruby:2.1 > > dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1 > > dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1 > > dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1 > > dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1 > > dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1 > > dev-ruby/rubygems-2.6.12 requires > > dev-lang/ruby:2.1 > > dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1 > > dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1 > > virtual/rubygems-13 requires dev-lang/ruby:2.1 > > virtual/rubygems-7 requires dev-lang/ruby:2.1 > > > > I tried a word ld update, but it didn't update any of those packages > > -- any ideas of how to fix? > > > > I use the following arguments when I run updates: > --update --deep --with-bdeps=y --changed-use --backtrack=120 > --keep-going world > > Do I need to use new-use instead?
I'm not sure; I always use new-use. If you haven't synced and updated recently, you may have issues as the default profiles still had ruby-2.1 listed in them. Alec
