Comments on: Rubygems 0.9.5 and Rails 1.2.6 – uninitialized constant Gem::GemRunner

By: Dirceu Jr.

Dirceu Jr. — Sun, 27 Jul 2008 23:59:15 +0000

Thanks!

Jared — Tue, 15 Jul 2008 20:17:58 +0000

Thanks, that saved me. I did have to delete the empty vendor/rails directory before it would work.

A thankful person — Tue, 20 May 2008 21:19:53 +0000

Thanks – this helped me a ton!

tedster — Sat, 19 Jan 2008 18:22:12 +0000

Andry, I also saw that problem after editing my framework.rake file.

I deleted the vender/rails subdirectory and fixed it (messes up my svn, but that’s easily fixed).

Steve Harris — Tue, 15 Jan 2008 17:01:09 +0000

Newbie question:

Why do you ‘rails:freeze:gems’ before ‘doc:rails’ ?

TIA

- Steve

GemRunner is no longer automatically required by Rubygems 0.9.5 « 3 Weeks — Thu, 06 Dec 2007 08:36:53 +0000

[...] isn’t required automatically now, which breaks the freezing of Rails. Florian Aßmann, bpdp have the fix: adding the require to [...]

Andry — Fri, 30 Nov 2007 02:04:05 +0000

I have found that I need to re-create dummy app (e.g complete remove dummy and recreate dummy again) after having framework.rake edited.

Apparently issuing rake:freeze:gems without edited framework.rake will create empty dummy/vendor/rails/ and that’s how the problem start.

I run rails 1.2.6 and rubygems 0.9.5 also on LinuxMint 4.0.