Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Upgrading with "rvm get stable" gives an incorrect error message regarding GPG keys #4533
In order to upgrade rvm with "rvm get stable", I needed to import pkuczynski's GPG key. The installation page gives correct instructions, telling the user to import both keys from the gnupg key servers. When attempting to upgrade rvm, without pkuczynski's key, it will fail, but the error message is as follows:
This error message should give the full line including the second key:
Additionally, in the instance that these servers are both inaccessible or these commands do not work for the user, importing directly from rvm.io is the fallback option. Unfortunately, both the installation page linked above and the error message from running "rvm get stable" only give the command to import the key belonging to mpapis, not pkuczynski's key. I only figured this out after seeing this comment on a different issue while searching for a solution. So, the error message and the installation page should show the full command to import the keys from rvm.io:
I know it was pkuczynski's key that made the difference, because when importing mpapis', gpg reported "not changed," whereas pkuczynski's key reported "imported."
I was on rvm 1.29.4 before upgrading. I upgraded because an "rvm install" attempt failed with the same gpg key error, and other members of my team were experiencing errors upgrading rvm with the same error.
This release was done in a bit of unmanaged fashion, apologies for that. We should first ensure new keys are distributed prior to running a release. Unfortunately, @mpapis has currently limited time and many people were waiting for the new release, while I was unaware of complications.
Follow instructions from http://rvm.io and you should be fine...
Issue is fixed in the latest release...
I had the same problem and at first I got a bit concerned because
I thought that the download server had been compromised and it was trying to install a tampered version.
I got and inspected the key