Ive ran into a brick wall trying to update one of my servers. I have been
using Gentoo for a long time but I haven't been following it as closely
for the past year so maybe there have been changes Im not aware of. Ive
already Googled and checked archives without really solving my problem.
When I try to update world I get this:
# emerge -uDatvk world
* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-ruby/rubygems:0
(dev-ruby/rubygems-2.0.14::gentoo, ebuild scheduled for merge) pulled in
by
>=dev-ruby/rubygems-2.0.2[ruby_targets_ruby20] required by
(dev-lang/ruby-2.0.0_p353::gentoo, installed)
dev-ruby/rubygems[ruby_targets_ruby20] required by
(virtual/rubygems-6::gentoo, ebuild scheduled for merge)
(dev-ruby/rubygems-2.0.14::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
!!! Enabling --newuse and --update might solve this conflict.
!!! If not, it might help emerge to give a more specific suggestion.
!!! All ebuilds that could satisfy "virtual/rubygems[ruby_targets_ruby18]"
have been masked.
!!! One of the following masked packages is required to complete your
request:
- virtual/rubygems-7::gentoo (masked by: ~x86 keyword)
- virtual/rubygems-5::gentoo (masked by: missing keyword)
(dependency required by "dev-ruby/rdoc-4.0.1-r1[-test]" [installed])
(dependency required by "dev-lang/ruby-2.0.0_p353[rdoc]" [installed])
(dependency required by "virtual/rubygems-6" [ebuild])
(dependency required by "dev-ruby/json-1.8.0" [installed])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
From reading other threads I have set RUBY_TARGETS in make.conf to be
"ruby19 ruby20" and Ive used eselect to set the default config to ruby19.
I have not been able to fix this problem so far.
Any ideas how to proceed?
--
