-
Notifications
You must be signed in to change notification settings - Fork 103
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
Puppet RVM looks for presence of gpg2, but RVM installer is agostic #82
Comments
Indeed, on Debian 7 (wheezy, stable), the binary is called "gpg" so this causes failures. |
For what its worth, gpg generally should be a symlink to gpg2, for example:
|
For completeness, ditto for CentOS 7.0:
|
Thanks Dominic, As a result of that, maybe we can just check for |
If only we had tests to run in actual servers,... beaker to the rescue |
Thanks @carlossg, seems to work well in production! |
Fix the installation on debian
The RVM install script will check if you have either
gpg2
orgpg
installed, and use either to validate the GPG signature.However, currently Puppet RVM only checks for gpg2 (and if it's found install the public key). This could lead to a confusing situation / failed provision if you have gpg installed: the installation will fail because puppet RVM hasn't downloaded the key (no gpg2 in the path!) but RVM's installed script wants to check the validity anyway (because it sees gpg in the path).
While this can be worked around (require the rvm GPG resource before Puppet installs RVM), it was.. rather surprising to see it fail and resulted in a lot of head scratching on my front.
TL; DR: can we check for
gpg
in addition togpg2
? And if either is there use the appropriate one to download the public key?The text was updated successfully, but these errors were encountered: