On Sat, Jan 18, 2014 at 5:55 AM, Mo Morsi wrote:
> On 01/18/2014 01:40 AM, Michael Stahnke wrote:
>
> On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram
> wrote:
>
> Hi
>
>
> On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote:
>
> Yes as others have mentioned puppet requires ruby(release) which
On Fri, Jan 17, 2014 at 10:40:07PM -0800, Michael Stahnke wrote:
> So should it just require ruby-mri?
That is my vote.
> > ... which is fine. However yum install puppet should be pulling in only
> > one. Not both. I would say almost everybody would expect that to be
> > ruby-mri
> I would say
On 01/18/2014 01:40 AM, Michael Stahnke wrote:
> On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram wrote:
>> Hi
>>
>>
>> On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote:
>>> Yes as others have mentioned puppet requires ruby(release) which is
>>> satisfied by both ruby-mri and jruby
> So should it j
On Fri, Jan 17, 2014 at 6:53 PM, Rahul Sundaram wrote:
> Hi
>
>
> On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote:
>>
>> Yes as others have mentioned puppet requires ruby(release) which is
>> satisfied by both ruby-mri and jruby
So should it just require ruby-mri?
The divergence from the way up
Hi
On Fri, Jan 17, 2014 at 9:43 PM, Mo Morsi wrote:
> Yes as others have mentioned puppet requires ruby(release) which is
> satisfied by both ruby-mri and jruby
>
... which is fine. However yum install puppet should be pulling in only
one. Not both. I would say almost everybody would expect
On 01/17/2014 05:34 PM, Martin Langhoff wrote:
> On Fri, Jan 17, 2014 at 5:24 PM, Bill Nottingham 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 han
