RVM 权限被拒绝错误

本文介绍了RVM 权限被拒绝错误的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我已经搜索过这个问题，但找不到相关的类似问题.如果这是重复的，请多多包涵.

I have searched for this problem and couldn't find relevant similar questions. Please bear with me if this is repetitive.

我已按照 RVM 网站中的指南安装 RVM，并且我已经安装了 rubies:

I have followed guides in RVM website to install RVM and I have installed rubies:

syed@rails:~$ rvm list rvm rubies ruby-1.8.7-p302 [ i386 ] => ruby-1.9.2-p0 [ i386 ]

如您所见，我已将 ruby​​-1.9.2 设为我的默认版本.

As you can see I have made ruby-1.9.2 my default.

这是我的 gem 目录:

This is my gem directory:

syed@rails:~$ rvm gemdir /home/syed/.rvm/gems/ruby-1.9.2-p0

现在，我尝试安装 rails，但出现以下错误:

Now, I tried to install rails and I am thrown the following error:

syed@rails:~$ gem install rails ERROR: While executing gem ... (Errno::EACCES) Permission denied - /home/syed/.gem/specs

我什至没有对错误产生任何影响:

I even did this without making any difference to the error:

syed@rails:~$ chown -R syed /home/syed/.rvm/

目前，我的环境是这样的:

Currently, my environment looks like this:

syed@rails:~$ gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.3.7 - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i686-linux] - INSTALLATION DIRECTORY: /home/syed/.rvm/gems/ruby-1.9.2-p0@rails3 - RUBY EXECUTABLE: /home/syed/.rvm/rubies/ruby-1.9.2-p0/bin/ruby - EXECUTABLE DIRECTORY: /home/syed/.rvm/gems/ruby-1.9.2-p0@rails3/bin - RUBYGEMS PLATFORMS: - ruby - x86-linux - GEM PATHS: - /home/syed/.rvm/gems/ruby-1.9.2-p0@rails3 - /home/syed/.rvm/gems/ruby-1.9.2-p0@global - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - rubygems/

我不明白为什么它试图将 gems 安装到我的系统 gem 目录路径?

I don't understand why it is trying to install gems to my system gem directory path?

推荐答案

我遇到了同样的问题，我通过执行以下操作解决了它:

I had this same problem and I resolved it by doing the following:

sudo mkdir ~/.gem/specs sudo chmod 777 ~/.gem/specs

似乎 RVM 正在尝试创建此specs"文件夹，但没有权限这样做.

It seems that RVM was trying to create this "specs" folder, but didn't have permissions to do so.