On 20 Lis, 22:17, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
> The frozen gems are the ones that merb is likely to use. Try using bin/merb
> and see what happens.

This helped me a lot. Seems there was something wrong with frozen gems
(or including both frozen and system gems on Macports Ruby, not sure).
When I moved gems/ directory away from the project, I got it up and
running.

Thanks a lot!
M.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to