Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I had this problem and the solution I found was somewhat unsatisfactory and temporary, but it worked.</p> <p>This error occurs during the <code>rubber:install_gems</code> task. After it fails, log into the ec2 server via ssh. At this point if you try to run <code>gem install rubber -v=2.1.2</code> manually in the remote console, it fails with the exact same error you show above. (the version number might be different for you, it depends on the rubber version you had when you did this).</p> <p>So now create an empty folder with any name, and create an almost-empty Gemfile inside it.</p> <pre><code>$ mkdir dummy &amp;&amp; cd dummy $ nano Gemfile </code></pre> <p>Then fill the Gemfile with the following contents:</p> <pre><code>source 'http://rubygems.org' gem 'rubber', '2.1.2' </code></pre> <p>Again, the version of rubber might be different for you.</p> <p>After creating this file, run <code>bundle install</code> and everything will install correctly. But don't ask me why it works differently when installing rubber via bundler than installing it via a plain old <code>gem install</code>.</p> <p>So after achieving this, logout from ec2 and re-run <code>cap rubber:bootstrap</code> and it should work.</p> <p>The unsatisfactory part is that if you decide to create new instances on ec2, it will fail again at the same point, and you'll have to repeat this steps and re-ignite the process manually for it to complete. So if any one can come up with a better solution like modifying rubber or something, let us know.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload