I've got RUBY_TARGETS="ruby18 jruby" in my /etc/make.conf. With that setting, dev-ruby/rubygems-1.3.6 fails to install for jruby: !!! ERROR: Package backport-util-concurrent was not found!
Created attachment 226407 [details] build log
Do earlier versions work?
(In reply to comment #2) > Do earlier versions work? I've got 1.3.5-r3 installed here, but re-emerging it fails with the same error. Had dev-java/jruby-1.4.0-r5 installed when last I merged jruby, and it's still that same version. Maybe dev-java/backport-util-concurrent is related. Had that installed in the past, but don't have it now. Maybe it should be a dep.
2010/02/09 17:10:23 caster Exp $ 09 Feb 2010; Vlastimil Babka <caster@gentoo.org> jruby-1.3.1-r1.ebuild, jruby-1.4.0-r4.ebuild, jruby-1.4.0-r5.ebuild: Remove backport-util-concurrent dependency as there seem to be no usage of it in jruby source anymore. Caster: maybe we do need it?
Or maybe jruby should have been revbumped when removing the dep: the list of jar files to load is hardcoded into the installed package, based on the *DEPEND variables; so if you retrospectively change an ebuild, --depclean will remove something that is still referenced during install.
Both solutions, either emerging backport-util-concurrent or remerging jruby, do work for me.
(In reply to comment #5) > Or maybe jruby should have been revbumped when removing the dep: the list of > jar files to load is hardcoded into the installed package, based on the *DEPEND > variables; so if you retrospectively change an ebuild, --depclean will remove > something that is still referenced during install. That's right and I know it. I'm sorry, no idea why I didn't revbump (probably was half-asleep). At least there was a revbump yesterday so updating world should fix itself. Also running java-check-environment should detect the problem and tell you to try remerge jruby. Installing backport-util-concurrent back is not recommended workaround.
