Rails - Jul 2005 - Just in case anyone else is having trouble with id2name

I have the latest version of the 0.13 pre-release from the rails
website.  I could not get rails to run.  There was some sort of
problem with id2name.  I traced the problem to glue with is a gem
package required by og and/or nitro.  I removed glue and consequently
the dependent packages and everything is working again.

-Dale

-- 
All creativity is an extended form of a joke.
 - Alan Kay

Did you investigate into what the problem was exactly? This happens to
me on Textdrive as well, where I don''t control the gem installations.

Joshua Sierles

On 7/2/05, Dale K. Hawkins
<dkhawk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> I have the latest version of the 0.13 pre-release from the rails
> website.  I could not get rails to run.  There was some sort of
> problem with id2name.  I traced the problem to glue with is a gem
> package required by og and/or nitro.  I removed glue and consequently
> the dependent packages and everything is working again.
> 
> -Dale
> 
> --
> All creativity is an extended form of a joke.
>  - Alan Kay
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

On 7/2/05, Joshua Sierles
<jsierles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Did you investigate into what the problem was exactly? This happens to
> me on Textdrive as well, where I don''t control the gem
installations.
I ran into this too on Textdrive, so I sat down with the breakpointer
and patched it.  http://dev.rubyonrails.com/changeset/1675

So either update your svn, use the beta gems (not sure if they go up
to rev 1675 yet), or wait for 0.13.

-- 
rick
http://techno-weenie.net