Require_gem is obsolete error


#1

Hi all,

I upgraded my gem, ruby and rails installations yesterday. The
versions are now respectively. Now, when I run the server I see this
warning message:

“/usr/local/bin/rake:17:Warning: require_gem is obsolete. Use gem
instead.”

and when I close it down I see this error message:

“Couldn’t find any pid file in ‘/Users/ian/projects/rails/atest/tmp/
pids’ matching ‘dispatch.[0-9]*.pid’
(also looked for processes matching “/Users/ian/projects/rails/atest/
public/dispatch.fcgi”)”

These happen even with a brand new created application (as in the
atest application shown here). I’m baffled because I hadn’t seen
these before. Can anyone point me to what may be going wrong?

Thanks,

Ian.

==== Transcript ====
lynley:~/projects/rails/atest ian$ script/server
=> Booting lighttpd (use ‘script/server webrick’ to force WEBrick)
=> config/lighttpd.conf not found, copying from /usr/local/lib/ruby/
gems/1.8/gems/rails-1.2.3/configs/lighttpd.conf
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server (see config/lighttpd.conf for options)
/usr/local/bin/rake:17:Warning: require_gem is obsolete. Use gem
instead.
^CExiting
Couldn’t find any pid file in ‘/Users/ian/projects/rails/atest/tmp/
pids’ matching ‘dispatch.[0-9]*.pid’
(also looked for processes matching “/Users/ian/projects/rails/atest/
public/dispatch.fcgi”)
/usr/local/bin/rake:17:Warning: require_gem is obsolete. Use gem
instead.
lynley:~/projects/rails/atest ian$
==== Transcript ====


#2

macfizz wrote:

Hi all,

I upgraded my gem, ruby and rails installations yesterday. The
versions are now respectively. Now, when I run the server I see this
warning message:

“/usr/local/bin/rake:17:Warning: require_gem is obsolete. Use gem
instead.”

and when I close it down I see this error message:

seems like rake is using require_gem instead of gem, seems pretty
harmless to me as it’s only a deprecation warning and otherwise doesn’t
modify the code in any sense.


#3

If you can, upgrade to rails 1.2.3. These errors go away in that
version.