Thanks, Matt, for watchdogging this. Efforts like yours has affected me and my learning MERB. And hopefully others. Rich
Matt Aimonetti wrote: > hehe so turned out I had the same problem and I didn't feel like > fixing the problem by any of the solutions given earlier. > > I fixed the problem by editing my dependencies.rb file as follows: > > dm_gems_version = "0.9.9" > > dependency "do_sqlite3", "0.9.10.1" # If using another database, > replace this > dependency "do_mysql", "0.9.10.1", :require_as => nil > dependency "dm-core", dm_gems_version > > > The problem is that some DM/DO dependencies use loose dependencies and > some use some hard dependencies. I'll talk with the DM guys to get > that fixed in a future release. > > Move the do_* adapters above dm-core and rebundle your app. > > thor merb:gem:install > > > - Matt > > > On Wed, Jan 7, 2009 at 6:43 PM, Richard Boldway <[email protected] > <mailto:[email protected]>> wrote: > > > I took a different approach in fixing my problem. > I followed the TroubleShooting instructions at > http://wiki.merbivore.com/howto/installation/gems. > How I'm fat dumb and happy. > > codeinnova wrote: > > An update on this. > > Like RickonRails i uninstalled the data_objects 0.9.10.1 > > > > gem uninstall data_objects -v 0.9.10.1 > > > > and it worked. > > So that means, when we upgrade merb, we have to have the specific > > versions of other dependent gems. is this right? > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
