Option to NOT install the r10k package about puppet-r10k HOT 9 CLOSED

Hi can you confirm what version of puppet you are using, this reminds me of a bug in the gem provider from a while back.

Also in the interim, I would suggest just using the config class if you dont want to handle the installation, you can see an example in the r10k class.

https://github.com/acidprime/r10k/blob/master/manifests/init.pp#L41-L52

Also when you say "Puppet package class." is the only difference the ensure => installed line vs ensure => 1.3.1

from puppet-r10k.

Here is the bug I was thinking of : https://projects.puppetlabs.com/issues/13397

from puppet-r10k.

seems simliar to #55

from puppet-r10k.

@fcntl bump, any update on what version of puppet you were using, this issue does not seem widespread so just want to identify the factors

from puppet-r10k.

worth mentioning here that you don't have to declare r10k, and could simple just declare r10k::config

from puppet-r10k.

I'm running Puppet v3.7.2 on CentOS 7:

Wrapped exception:
Execution of '/usr/bin/gem install -v 1.3.4 --no-rdoc --no-ri r10k ' returned 1: ERROR:  Can't use --version w/ multiple gems. Use name:ver instead.
Error: /Stage[main]/R10k::Install/Package[r10k]/ensure: change from absent to 1.3.4 failed: Could not update: Execution of '/usr/bin/gem install -v 1.3.4 --no-rdoc --no-ri r10k ' returned 1: ERROR:  Can't use --version w/ multiple gems. Use name:ver instead.

from puppet-r10k.

@acidprime was always the latest version of Puppet at the time, probably 3.7.1 or 3.7.2. RHEL6.5.

from puppet-r10k.

@fcntl, what version of Ruby are you running on your puppet master?

from puppet-r10k.

This is likely going to be needed for v3 anyway due to some PE changes.

from puppet-r10k.