With guys on the IRC (which is ghost town nowadays) I've end up with the working Merb + Bundling on Ruby 1.9.1.
What works for me: - mac os 10.5 - ruby 1.9.1 p243 - rubygems 1.3.1 - DEFAULT in ruby, DON'T EVEN TRY TO UPGRADE - Merb from edge.merbivore.com - thor from edge.merbivore.com After you apply some known patches, thor tasks, templater (from github), patch pg gem, patch merb-mailer, use pk-merb_sequel Yehuda the new bundler would do soo much good. I don't know but this is somehow much more important for me than the new router. ;-) Also the Lighthouse cleanup which I'm willing to help with would be huge help for remaining Merb comunity. Pavel On Aug 9, 9:52 pm, Pavel Kunc <[email protected]> wrote: > The Bundling and Ruby 1.9.1 + GEMs 1.3.5 or any other than bundled > with the Ruby 1.9.1 (1.3.1) is huge pain in the arse! > > I'm able to fix couple of issues with code which Jacques suggests, > however this just works on the 1.3.1 gems and on any other version it > just fails with following exception which I don't understand. > > If you generate fresh app on Ruby 1.9.1p243 and gem update --system > (1.3.5) You'll end you bundled live with this crap:http://pastie.org/577758 > > Notice that if you use non bundled version of commands (rake, merb, > spec) everything works but if you use Bundled versions (./bin/*) > everything fails this way. Does anybody have any idea??? I'm > struggling with this for a long time. > > Pavel > > On Aug 8, 3:59 pm, Christian Hoeppner <[email protected]> wrote: > > > > > As much as I would have loved this to work, it gives me the same > > problem. I've traced it down to here: > > > lib/thor.rb:140 > > > > new(args, opts, config).invoke(task, trailing || []) > > > As you can see it calls the constructor with 3 arguments. Yet... > > > merb.thor/main.thor > > > > module Merb > > > > class Gem < Thor > > > extend ColorfulMessages > > > > def initialize > > > ..... > > > Here the constructor is being defined without arguments. Turns out the > > problem wasn't rubygems at all, but the upgraded Thor. Jacques is right, > > merb.thor needs to be upgraded. I'm going to wait for wycats to do his > > release and report back. > > > Thanks everyone! > > > El vie, 07-08-2009 a las 21:50 -0700, Jacques Crocker escribió: > > > > I definitely don't recommend downgrading RubyGems. The best fix in the > > > short term is to just make the code fix in tasks/merb.thor. Here's > > > what I currently use which seems to work ok on 1.0.12: > > > > tasks/merb.thor/gem_ext.rb > > >http://gist.github.com/164302 > > > > for good measure, you might want to try swap this file as well > > > (ignores the gem confirmation step, which most often reports failure, > > > even when things worked fine) > > > tasks/merb.thor/main.thor > > >http://gist.github.com/164301 > > > > wycats new bundler is looking pretty awesome on github. Looking > > > forward to the upgrade! > > > > On Aug 7, 8:11 pm, "Michael D'Auria" <[email protected]> wrote: > > > > Try downgrading rubygems to a lower version, I believe 1.3.2 will work. > > > > > Michael > > > > > On 8/7/09, Christian Hoeppner <[email protected]> wrote: > > > > > > I found this while configuring a production server this morning. I > > > > > loaded the server up, installed ruby & rubygems 1.3.5, cloned my app, > > > > > and... > > > > > >> ch...@ubuntu:/var/merb/raider/current$ bin/thor merb:gem:install > > > > >> [WARNING] Attempted to create task "full_list" without usage or > > > > >> description. Call desc if you want this method to be available as > > > > >> task or > > > > >> declare it inside a no_tasks{} block. Invoked from > > > > >> "/var/merb/raider/releases/20090807214032/tasks/merb.thor/ops.rb:23". > > > > >> [WARNING] Attempted to create task "rescue_failures" without usage or > > > > >> description. Call desc if you want this method to be available as > > > > >> task or > > > > >> declare it inside a no_tasks{} block. Invoked from > > > > >> "/var/merb/raider/releases/20090807214032/tasks/merb.thor/ops.rb:38". > > > > >> [WARNING] Attempted to create task "list" without usage or > > > > >> description. > > > > >> Call desc if you want this method to be available as task or declare > > > > >> it > > > > >> inside a no_tasks{} block. Invoked from > > > > >> "/var/merb/raider/releases/20090807214032/tasks/merb.thor/main.thor:34:in > > > > >> `load_thorfile'". > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/../lib/thor.rb:140:in > > > > >> `initialize': wrong number of arguments (3 for 0) (ArgumentError) > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/../lib/thor.rb:140:in > > > > >> `new' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/../lib/thor.rb:140:in > > > > >> `start' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/base.rb:351:in > > > > >> `start' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/../lib/thor.rb:127:in > > > > >> `start' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/runner.rb:31:in > > > > >> `method_missing' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/task.rb:29:in > > > > >> `send' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/task.rb:29:in `run' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/invocation.rb:108:in > > > > >> `invoke' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/invocation.rb:115:in > > > > >> `call' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/invocation.rb:115:in > > > > >> `invoke' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/../lib/thor.rb:140:in > > > > >> `start' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/lib/thor/base.rb:351:in > > > > >> `start' > > > > >> from > > > > >> /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/../lib/thor.rb:127:in > > > > >> `start' > > > > >> from /usr/lib/ruby/gems/1.8/gems/thor-0.11.5/bin/thor:7 > > > > >> from bin/thor:31:in `load' > > > > >> from bin/thor:31 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
