updates have been blocked for weeks on my computer because of some weird ruby stuff with no way to know what's going on I can't update anymore. At first i thought it would be fixed soon so i decided to just wait, but it's been so for weeks now. Other people on irc have the same problems. Some of them managed to make portage happy by masking some packages, but i dont manage to find the right packages to mask. Reproducible: Always Steps to Reproduce: 1.emerge world -Dqvtau Actual Results: The following USE changes are necessary to proceed: #required by dev-ruby/rdoc-3.12[ruby_targets_ruby19], required by dev-lang/ruby-1.9.3_p0[rdoc], required by dev-ruby/rake-0.9.2.2[ruby_targets_ruby19], required by dev-ruby/json-1.6.4[-test,-doc,ruby_targets_ruby18] >=dev-ruby/racc-1.4.7 ruby_targets_ruby19 #required by virtual/rubygems-4, required by dev-ruby/json-1.6.4[-test,ruby_targets_ruby19], required by dev-ruby/rdoc-3.12[ruby_targets_ruby19], required by dev-lang/ruby-1.9.3_p0[rdoc], required by dev-ruby/rake-0.9.2.2[ruby_targets_ruby19], required by dev-ruby/racc-1.4.7[-test,-doc,ruby_targets_ruby19] >=dev-ruby/rubygems-1.8.15 ruby_targets_ruby19 #required by dev-ruby/json-1.6.4[-test,-doc,ruby_targets_ruby18], required by dev-ruby/rdoc-3.12[ruby_targets_ruby19], required by dev-lang/ruby-1.9.3_p0[rdoc], required by dev-ruby/rubygems-1.8.15[ruby_targets_ruby19], required by virtual/rubygems-1, required by dev-ruby/racc-1.4.7[-test,ruby_targets_ruby18] >=dev-ruby/rake-0.9.2.2 ruby_targets_ruby19 #required by dev-lang/ruby-1.9.3_p0[rdoc], required by dev-ruby/rake-0.9.2.2[ruby_targets_ruby19], required by dev-ruby/json-1.6.4[-test,-doc,ruby_targets_ruby18] >=dev-ruby/rdoc-3.12 ruby_targets_ruby19 #required by dev-ruby/rdoc-3.12[ruby_targets_ruby19], required by dev-lang/ruby-1.9.3_p0[rdoc], required by dev-ruby/rake-0.9.2.2[ruby_targets_ruby19], required by dev-ruby/racc-1.4.7[-test,-doc,ruby_targets_ruby19] >=dev-ruby/json-1.6.4 ruby_targets_ruby19 Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT). Expected Results: At least some information about what triggers those ruby stuff..? I dont use ruby, i have nothing ruby-related installed. I barely even knew about ruby before this. I've tried masking all those ruby stuff, but this wont fix the probleme. It's even worse: portage wants (--automask) to unmask them. I've also tried adding RUBY_TARGETS="ruby18" to my make.conf, doesn't change anything.
Created attachment 299429 [details] emerge --info
It seems that a circular dependency is preventing the autounmask dependency chain from showing how it all got pulled in. If you set USE="-rdoc" to break the cycle, then maybe it will show a better dependency chain.
You should also use -N, as missing it may confuse emerge in such cases. Us --autounmask-keep-masks to prevent emerge from reverting your masks.
@zac: This is weird, but 'ufed' shows that rdoc is NOT set. If i do 'grep rdoc /etc/make.conf /etc/portage/ -R' nothing shows up. I dont know why portage thinks +rdoc. So i've added USE=-rdoc to command line (and also added -rdoc in USE in make.conf), and indeed, this fixes the problem. How is it that ufed is not to be trusted ? How can i know which use flags are set in my current set up ? (bonus point if i can know from where they are set/unset). I also have a dep problem with kde about [=aqua]... but ufed doesn't know about 'aqua' !? @few: Thanks for the hints. --autounmask-keep-masks is so helpful i think i'm gonna add it to my 'emerge' alias. I dont know if I should close the ticket as changing rdoc is not solving the actual problem (portage/emerge is lost).
additional note, after investigation, it seems that ruby is pulled by dev-texlive/texlive-pictures-2011 which is pulled by texlive. I wonder how this is. texlive was ruby-free until recently.
Maybe this has something to do with bug #399681?
