# Require\_gem is obsolete error

**URL:** <https://www.ruby-forum.com/t/require-gem-is-obsolete-error/88991>\
**Category:** Rails\
**Created:** [March 16, 2007, 10:11am UTC](https://www.ruby-forum.com/t/require-gem-is-obsolete-error/88991 "2007-03-16T10:11:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![macfizz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b9bd4f/32.png) [@macfizz](https://www.ruby-forum.com/u/macfizz)\
**Post date:** [March 16, 2007, 10:11am UTC](https://www.ruby-forum.com/t/require-gem-is-obsolete-error/88991/1 "2007-03-16T10:11:46Z")

</div>

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](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 ====

---

<div class="post-metadata">

**Author:** ![macfizz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b9bd4f/32.png) [@macfizz](https://www.ruby-forum.com/u/macfizz)\
**Post date:** [March 16, 2007, 4:56pm UTC](https://www.ruby-forum.com/t/require-gem-is-obsolete-error/88991/2 "2007-03-16T16:56:15Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![macfizz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b9bd4f/32.png) [@macfizz](https://www.ruby-forum.com/u/macfizz)\
**Post date:** [March 17, 2007, 8:03am UTC](https://www.ruby-forum.com/t/require-gem-is-obsolete-error/88991/3 "2007-03-17T08:03:34Z")

</div>

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