Merb bundler currently has a few issues with upgrading either the merb or datamapper version numbers. There's a circular dependency issue in there somewhere.
For a temporary workaround, open up taks/merb.thor/main.thor and find the "def confirm" method. I went ahead and commented that out, and things have been working fairly well for me since then. I'm hoping to add some major improvements in the merb bundler for 1.1. This includes choosing the source per dependency, better dependency tracking, and a way to install gems locally (hybrid of gem:redeploy and gem:install). I'll be working with Yehuda next week on getting these changes merged in On Apr 14, 1:55 pm, dc <[email protected]> wrote: > hi - > > playing with the merb bundler to try and see if working with merb gems > is still a conflict point > > thor merb:gem:install > > .... > > Installing merb_datamapper-0.9.9 > - Successfully uninstalled merb_datamapper-0.9.8 > Needed merb-core (>= 1.0.11, runtime) for merb-action-args (= 1.0.11, > runtime), but could not find it > Found merb-core-0.9.13 > Rolling back transaction > > so, the bundler cant find the latest merb-core ??? > or does it somehow look for a local cache first (it seems to find the > previously installed version rather than the latest) > this doesnt seem to really address dependencies. > > [...@metroid:dev/mb1]$ gem install merb-core > Successfully installed merb-core-1.0.11 > 1 gem installed > > [...@metroid:dev/mb1]$ gem list merb > *** LOCAL GEMS *** > merb-core (1.0.11) > > .. well, that way is ok. > > [...@metroid:dev/mb1]$ bin/merb > Loading init file from /Users/dc/svn/ddunit/dev/mb1/config/init.rb > loading dm... > finished loading dependencies > before_app > after_app > DONE init > Loading /Users/dc/svn/ddunit/dev/mb1/config/environments/ > development.rb > loading development > DONE loading development > ~ > ~ FATAL: The gem merb-action-args (= 1.0.11, runtime), [] was not > found > > I tried rolling back a version: > # dependencies are generated using a strict version, > merb_gems_version = "1.0.10" > > but then just get the same error but a version earlier. > > - Successfully uninstalled merb_datamapper-0.9.8 > Needed merb-core (>= 1.0.10, runtime) for merb-action-args (= 1.0.10, > runtime), but could not find it > Found merb-core-0.9.13 > Rolling back transaction > [...@metroid:dev/mb1]$ > > wondering if there are any changes afoot to fix merb gems hell > or is improvement abandoned now on the way to rails3? > > /dc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
