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 Mon, Jan 20, 2014 at 10:29 AM, Vít Ondruch wrote:
>> Seems to be bug. Haven't seen any bug report from you yet, so I did one
>> for you: https://github.com/bkabrda/rubypick/issues/4
>
>
> https://admin.fedoraproject.org/updates/rubypick-1.1.1-1.fc20
> https://admin.fedoraproject.org/updates/rub
Dne 20.1.2014 11:48, Vít Ondruch napsal(a):
> Dne 17.1.2014 23:34, Martin Langhoff napsal(a):
>> 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. Yo
Dne 17.1.2014 23:34, Martin Langhoff napsal(a):
> 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
Dne 18.1.2014 07:40, Michael Stahnke napsal(a):
> 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
On Fri, Jan 17, 2014 at 07:36:44PM -0500, Matthew Miller wrote:
> On Fri, Jan 17, 2014 at 05:25:22PM -0500, Martin Langhoff wrote:
> > Alright, I think I know what's happening: yum resolves the dep on ruby
> > by installing jruby AND ruby-mri
> >If I do yum install ruby ; yum install puppet, then t
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
On Fri, Jan 17, 2014 at 05:25:22PM -0500, Martin Langhoff wrote:
> Alright, I think I know what's happening: yum resolves the dep on ruby
> by installing jruby AND ruby-mri
>If I do yum install ruby ; yum install puppet, then things make sense. See
We had this before and there was a workaround. I'
Bill Nottingham writes:
> Martin Langhoff (martin.langh...@gmail.com) said:
>> Puppet (the client side, at least) should be installable with
>> relatively thin deps, so it can manage lightweight hosts...
>>
>> I am having trouble disentangling which deps to file a bug against;
>> maybe virt-what
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 handle that.
What's happening however is that I am getti
On Fri, Jan 17, 2014 at 5:07 PM, Martin Langhoff
wrote:
> Puppet (the client side, at least) should be installable with
> relatively thin deps, so it can manage lightweight hosts...
>
> I am having trouble disentangling which deps to file a bug against;
> maybe virt-what ?
Alright, I think I know
Martin Langhoff (martin.langh...@gmail.com) said:
> Puppet (the client side, at least) should be installable with
> relatively thin deps, so it can manage lightweight hosts...
>
> I am having trouble disentangling which deps to file a bug against;
> maybe virt-what ?
You need to make sure your t
Puppet (the client side, at least) should be installable with
relatively thin deps, so it can manage lightweight hosts...
I am having trouble disentangling which deps to file a bug against;
maybe virt-what ?
[martin@tp-martin puppet-rlgold.git]$ sudo yum install puppet
[sudo] password for martin:
17 matches
Mail list logo
