Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to NOT install the r10k package #74

Closed
ghost opened this issue Sep 1, 2014 · 9 comments
Closed

Option to NOT install the r10k package #74

ghost opened this issue Sep 1, 2014 · 9 comments
Labels
bug Something isn't working
Milestone

Comments

@ghost
Copy link

ghost commented Sep 1, 2014

Ge this horrible broken error when trying to install r10k gem using this module:

Error: Could not update: Execution of '/usr/bin/gem install -v 1.1.0 --no-rdoc --no-ri r10k ' returned 1: ERROR: Can't use --version w/ multiple gems. Use name:ver instead.
Wrapped exception:
Execution of '/usr/bin/gem install -v 1.1.0 --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 1.3.2 to 1.1.0 failed: Could not update: Execution of '/usr/bin/gem install -v 1.1.0 --no-rdoc --no-ri r10k ' returned 1: ERROR: Can't use --version w/ multiple gems. Use name:ver instead.
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygems-bundler' returned 1: Error: No matching Packages to list
Error: /Stage[main]/Ruby::Dev/Package[rubygems-bundler]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygems-bundler' returned 1: Error: No matching Packages to list

It worked fine when I was installing it using my own Puppet package class. Please add an option to NOT install the r10k package.

@acidprime
Copy link
Collaborator

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

@acidprime
Copy link
Collaborator

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

@acidprime
Copy link
Collaborator

seems simliar to #55

@acidprime
Copy link
Collaborator

@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

@acidprime
Copy link
Collaborator

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

@eoly
Copy link

eoly commented Oct 28, 2014

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.

@ghost
Copy link
Author

ghost commented Nov 5, 2014

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

@elyscape
Copy link
Contributor

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

@acidprime acidprime added the bug Something isn't working label Feb 23, 2015
@acidprime acidprime added this to the Version 3.0 milestone Mar 20, 2015
@acidprime
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants