Upgrade failed after the recent today's commits: «cannot load such file -- rails_multisite»

(Discourse.PRO) #1


Tested in Vagrant.

LoadError: cannot load such file – rails_multisite
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:76:in require' /var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:76:inblock (2 levels) in require’
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:72:in each' /var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:72:inblock in require’
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:61:in each' /var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:61:inrequire’
/var/lib/gems/2.2.0/gems/bundler-1.9.4/lib/bundler.rb:134:in require' /vagrant/config/application.rb:15:in<top (required)>’
/vagrant/Rakefile:5:in require' /vagrant/Rakefile:5:in<top (required)>’

Vagrant based server failing on db:migrate
Discourse as Your First Rails App
Rails Multisite still breaking build
(Régis Hanol) #2

I cannot reproduce this issue. I just successfully upgraded http://discourse.codinghorror.com to latest.


I encountered the same problem after upgrading.

I did followings to fix it.

Add this in Gemfile before line 41

gem 'rails_multisite'

and then it’ll complain that it can’t load


just go into the directory and run command

sudo chmod a+r generators.rake

Now, db:migrate will execute correctly.

(Sam Saffron) #4

it was broken for 1 commit, perhaps rubygems did not propagate fast enough, still an issue?

Rails Multisite still breaking build
(Jeff Atwood) #5

(Matt Palmer) #6

There are actually several files with the restrictive permissions. You’ll need to run:

sudo chmod -R a+r /var/lib/gems/2.2.0/gems/rails_multisite-1.0.1

To fix them all up.