F20: Puppet depchain pulls in Java

Mo Morsi mmorsi at redhat.com
Sat Jan 18 02:43:37 UTC 2014

On 01/17/2014 05:34 PM, Martin Langhoff wrote:
> On Fri, Jan 17, 2014 at 5:24 PM, Bill Nottingham <notting at 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.

Yes as others have mentioned puppet requires ruby(release) which is
satisfied by both ruby-mri and jruby


By installing one before hand, you are expressing your preference and
from there on the package system will see the dependency as being
resolved (eg when installing puppet).

> Interestingly enough, after uninstalling jruby, rubypick still thinks
> it's installed!

Arg sounds like a bug, would file an issue:


Rubypick is sort of a fedora-specific rvm like tool, it allows us to
synergize with upstream practices while providing a powerful interface
based on our tooling and methodology.

A few of us have been working on a similar tool for bundler, as well as
some generic ruby post processing tools here:


> [martin at 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 at 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 :-)

We're working towards improving it! Any feedback & contributions would
be more than appreciated!


More information about the devel mailing list