I'm trying to load the console of any of the projects on my development
machine.
bash$ ruby script/console
Loading development environment.
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/console.rb:25:in
`exec': No such file or directory - irb -r irb/completion -r
script/../config/../config/environment -r console_app -r
console_with_helpers --simple-prompt (Errno::ENOENT)
from
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/console.rb:25
from
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
from
/usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in
`require'
from script/console:3
Any ideas would be much appreciated.
Thanks
on 08.09.2006 02:27
on 10.09.2006 05:29
Alright, Solved the problem. Apparently irb wasn't linked properly in Ubuntu Dapper. I resolved the problem by doing a: sudo ln -s /usr/bin/irb1.8 /usr/bin/irb Hope this can help someone else in the future :)
on 18.09.2006 05:59
Jesse Bain wrote: > Alright, Solved the problem. Apparently irb wasn't linked properly in > Ubuntu Dapper. I resolved the problem by doing a: > sudo ln -s /usr/bin/irb1.8 /usr/bin/irb > > Hope this can help someone else in the future :) Well done! Thank you for taking the time to answer back on your original post. This helped me out and saved me a lot of time. Thanks again. I wonder if there is a buglist for this in launchpad or something? I will look into it.
on 03.02.2007 13:10
Jesse Bain wrote: > Alright, Solved the problem. Apparently irb wasn't linked properly in > Ubuntu Dapper. I resolved the problem by doing a: > sudo ln -s /usr/bin/irb1.8 /usr/bin/irb > > Hope this can help someone else in the future :) Thanks for the tip! I had the same problem with Edgy. My console is working great now.
on 06.02.2007 22:20
Landy Defield wrote: > Well done! Thank you for taking the time to answer back on your original > post. This helped me out and saved me a lot of time. Thanks again. > I wonder if there is a buglist for this in launchpad or something? I > will look into it. Me again.. I was running into this problem on a new Ubuntu Feisty install and spent a few minutes looking through Google to figure out why I was getting this error. Stumbled across this topic having completely forgotten about it. Makes me glad I wrote it down *somewhere* :)
on 12.02.2007 00:06
Thank you! Fixed my problem in Edgy.
on 18.02.2007 21:38
Thanx a lot for the solution, i faced the same problem, and u saved me a lot of time.
on 22.03.2007 13:02
Jesse Bain wrote: > Alright, Solved the problem. Apparently irb wasn't linked properly in > Ubuntu Dapper. I resolved the problem by doing a: > sudo ln -s /usr/bin/irb1.8 /usr/bin/irb > > Hope this can help someone else in the future :) You hero. Thanks so much for posting this. Used it on Edgy Eft Ubuntu. Let's make it known...
on 16.04.2007 10:36
Very helpful. Many thanks for posting this! :-)
on 17.04.2007 12:18
Yet Another Thanks! I am running a fresh install of Debian 4.0 Etch (stable). Why is this problem still around..? :)
on 13.05.2007 21:48
helped here too. etch still around...
on 30.05.2007 15:27
In case anyone was wondering, this problems occurs if you install irb1.8 and NOT the irb dependency package. If you have already installed irb1.8, just do an "apt-get install irb" and the problem should be fixed.
on 31.05.2007 23:42
Jesse Bain wrote: > Alright, Solved the problem. Apparently irb wasn't linked properly in > Ubuntu Dapper. I resolved the problem by doing a: > sudo ln -s /usr/bin/irb1.8 /usr/bin/irb > > Hope this can help someone else in the future :) it does ! :) (ubuntu 7.4 - feisty) thanks a lot [smiley holding a flower]
on 22.09.2007 06:18
This just now helped me, so I thought I'd keep it alive. It would be nice, though, if the Ubuntu team would get their crap together. There is no excuse for the sorry state of ruby/rails on Feisty (or earlier versions, for that matter).
on 18.11.2007 09:26
This also just saved me a bit of researching - thanks Jesse!