On Fri, Jan 17, 2014 at 5:24 PM, Bill Nottingham <nott...@redhat.com> wrote: > You need to make sure your transaction is pulling in classic ruby > rather than jruby.
Well, ideally something in the dep data should indicate a preference, and the depsolver should handle that. What's happening however is that I am getting both classic ruby (which rubypick calls "ruby-mri") AND jruby installed. Interestingly enough, after uninstalling jruby, rubypick still thinks it's installed! [martin@tp-martin puppet-rlgold.git]$ ruby --help This is Fedora's rubypick - a Ruby runtime chooser. You can use it to execute Ruby programmes with any Fedora Ruby runtime. These currently include: Ruby - binary /usr/bin/ruby-mri - Installed JRuby - binary /usr/bin/jruby - Installed To run a specific runtime, use: ruby _mri_ [params] ruby _jruby_ [params] The default is _mri_. (...) [martin@tp-martin puppet-rlgold.git]$ stat /usr/bin/jruby stat: cannot stat ‘/usr/bin/jruby’: No such file or directory The whole thing seems... suboptimal :-) m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
