Hi Tom!, I can't assure this, but for me your trouble seems to be a Ruby Gems issue, not Radiant's.
I have installed Radiant from gem in different machines and environments (Linux, OS X, Windows-Cygwin) and never had any issues with the installation. Except with sqlite3, but i believe that this is not your case. Ubuntu is Debian based, and this distro has been critiqued by the packaging policy of Ruby and associated tools. The problems is that the Ruby interpreter/tools is scattered across many packages, and you must install all of them to avoid problems. More info in: http://paulgoscicki.com/archives/2005/09/ruby-on-rails-on-ubuntu/ and http://del.icio.us/tag/ruby%2Bdebian /AITOR On Tue, Mar 11, 2008 at 7:43 PM, Tom Cloyd <[EMAIL PROTECTED]> wrote: > I don't want to waste anyone's time, and I myself can be of little or no > use in relation to this possible issue as I'm too new to all the > technology involved - Ruby, Radiant, and Kubuntu Linux. But I can sketch > out the events and possible problem. > > I'm running Kubunu 7.10 Linux, and Ruby 1.8.6. A few days ago I > attempted in install radiant, following the instructions on > http://radiantcms.org/download/. > > I issued the command > > % gem install --include-dependencies radiant > > Then I tried the next one on that page... > % radiant --database sqlite3 path/to/project > > and got an error I couldn't make sense of. I think it was this one... > > /usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError) > > From this point on, all attempts to reference rubygems interactively > got this same error. > > Somehow I got onto the #radiantcms irc channel and got some help - I was > told that it appeared that my rubygems had gone bad. > > Since then I have upended the earth trying to get things back to normal. > Twice I posted to the ruby talk list about this problem, and got nothing > back. I reinstalled rubygems every way I could think of and learn about. > Nothing worked. > > This morning, someone else posted this identical error message to > ruby-talk, asking for help. He stated that it happened after he issued > to his Ubuntu linux the command: > > sudo gem update --system > > He was told that was a no-no. Reference was made to > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452547 > > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/279841 > > He was told how to fix it, and I followed the instructions, and got back > my rubygems. > > Now...I write because I'm thinking that there may be something in the > radiant gem install which causes this breakage - either something like > that "gem update --system" command, or something similar. > > I can't check this out. Too ignorant. Maybe someone else will want to. > > This was a nasty mess, and I've been utterly stuck for several days, > until this morning. > > Hope this helps 'the cause'. If not, ignore it. > > Now I'm off to see if I can finish the radiant setup, so I can begin > learning how to use this thing. > > t. > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Tom Cloyd, MS MA, LMHC > Private practice Psychotherapist > Bellingham, Washington, U.S.A: (360) 920-1226 > << [EMAIL PROTECTED] >> (email) > << TomCloyd.com >> (website & psychotherapy weblog) > << sleightmind.wordpress.com >> (mental health issues weblog) > << directpathdesign.com >> (web site design & consultation) > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
