I just found out about the --prerelease option to gem install, which did the trick. Anyway, I got it to build by using dups of the frozen strings when assigning them to gemspec version. Quite dumb, really. I couldn't find out what the problem was in Jeweler after digging through it's source code. A frozen string is just a string that can't change, right? So what is Jeweler trying to do with it?
2010/3/4 Pavel Kunc <[email protected]> > Yep the Version constants are problematic. It's a shame we can't have > them frozen. They should be constants dammit. > > Pavel > > On Mar 2, 10:08 pm, Michishige Kaito <[email protected]> wrote: > > Dumb me, should check where I clone from next time... > > > > Anyways, I found that the frozen string > > MERB::Version, Merb::ActionArgs::VERSION, isn't being liked by Jeweler > when > > assigning it to gemspec.version. > > > > 2010/3/2 Michishige Kaito <[email protected]> > > > > > > > > > I'm trying to install git HEAD, but on rake install, I get a load of > "no > > > such file to load -- extlib/tasks/release". I made sure extlib is > installed, > > > even got the one from datamapper git HEAD, but there's nothing such as > > > "release" in there... > > > > > 2010/3/2 Pavel Kunc <[email protected]> > > > > > Both your problems will solve using proper version for Ruby 1.9.x. > > > > >> Merb 1.0.x is NOT Ruby 1.9.x compatible use Merb 1.1.0.pre gems. > > > > >> Pavel > > > > >> On Mar 2, 6:46 pm, Michishige Kaito <[email protected]> wrote: > > >> > While at it, I was also getting these: > > > > >> > /usr/lib/ruby/gems/1.9.1/gems/merb-core-1.0.15/lib/merb-core/dispatch/route > > >> r/behavior.rb:18: > > >> > warning: undefining `object_id' may cause serious problem > > > > >> > /usr/lib/ruby/gems/1.9.1/gems/merb-core-1.0.15/lib/merb-core/dispatch/route > > >> r/behavior.rb:18: > > >> > warning: undefining `__send__' may cause serious problem > > > > >> > Maybe someone is interested and wants to fix it. I don't know enough > > >> about > > >> > merb internals. > > > > >> > 2010/3/2 Michishige Kaito <[email protected]> > > > > >> > > As stated above: > > > > >> > > /usr/lib/ruby/site_ruby/1.9.1/rubygems/version.rb:186:in `strip!': > > >> can't > > >> > > modify frozen string (RuntimeError) > > > > >> > > This is caused > > >> > > because > > >> > /usr/lib/ruby/gems/1.9.1/gems/merb-core-1.0.15/lib/merb-core/bootloader.rb: > > >> 454:in > > >> > > `new' calls Gem::Version.new(RUBY_VERSION), where RUBY_VERSION > seems > > >> to be a > > >> > > frozen string. #new calls #strip! on the frozen string, causing > the > > >> > > RuntimeError. > > > > >> > > Editing version.rb seemed way too hacky, so I edited merb's > > >> bootloader.rb > > >> > > to pass a dup of RUBY_VERSION instead. > > > > >> > > Although, this is probably a bug with either ruby itself, or > rubygems. > > > > >> -- > > >> 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]<merb%[email protected]>< > merb%[email protected]<merb%[email protected]> > >. > > >> For more options, visit this group at > > >>http://groups.google.com/group/merb?hl=en. > > -- > 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] <merb%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > > -- 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.
