Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Error: While executing gem ... invalid option: --no-rdoc #2838

Open
alex-kusakin opened this issue May 10, 2019 · 5 comments
Open

Error: While executing gem ... invalid option: --no-rdoc #2838

alex-kusakin opened this issue May 10, 2019 · 5 comments

Comments

@alex-kusakin
Copy link

When I run default puphpet configuration, it fails with error:

Error: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 1.2.1 --no-rdoc --no-ri deep_merge' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> machine1:     invalid option: --no-rdoc

It seems like it started reproducing on rvm 1.29.8 (latest version), because it works on rvm 1.29.7.

It is reproduced on default Puphpet configuration, just open https://puphpet.com and build configuration with all default settings (just click "continue" on every step), then download archive, and run "vagrant up".

As a temporary solution, set older rvm version (1.29.7) in puphpet/puppet/modules/rvm/manifests/system.pp , replace line 3 with:
$version="1.29.7",

What may the better solution be, so that we will have latest rvm and valid configuration?

@chall8908
Copy link

This is due to a change in the gem command in versions > 3, not really RVM itself. My own reading of the gem provider defined here (and some testing) shows that setting source => 'https://rubygems.org' will cause the gem installation to skip adding the--no-rdoc and --no-ri flags which are no longer present on newer rubygems.

@bastos71
Copy link

I don't know where to put it, but I guess here seems right : updating the file puphpet/puppet/modules/rvm/lib/puppet/provider/rvm_gem/gem.rb in the box archive will solve this issue :

...
l.112      command << "--no-document" <<  resource[:name]
...

@codingXllama
Copy link

I don't know where to put it, but I guess here seems right : updating the file puphpet/puppet/modules/rvm/lib/puppet/provider/rvm_gem/gem.rb in the box archive will solve this issue :

...
l.112      command << "--no-document" <<  resource[:name]
...

How do you do that?

@bastos71
Copy link

I don't know where to put it, but I guess here seems right : updating the file puphpet/puppet/modules/rvm/lib/puppet/provider/rvm_gem/gem.rb in the box archive will solve this issue :

...
l.112      command << "--no-document" <<  resource[:name]
...

How do you do that?

With your prefered text editor ^^

@moroz-igor
Copy link

Oh my God) Finally I've solved it) Thanks, Friend!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants