Comments and changes to this ticket
-
Jim May 26th, 2008 @ 07:55 PM
- → Title changed from “C” to “Can't run specific(old) merb versions”
Merb can't be 'soft' frozen. That is, after installing 0.9.3 and running merb 0.9.2 on a 0.9.2 project, it still tries to load merb-core 0.9.3:
rubygems.rb:319:in `activate':
can't activate merb-core (>= 0.9.3), already activated merb-core-0.9.2] (Gem::Exception)
-
-
Jim May 27th, 2008 @ 02:30 AM
irb(main):004:0> gem 'merb-core'
=> false
irb(main):005:0> gem 'merb-core', "= 0.9.2"
=> false
irb(main):006:0> gem 'merb-core', "= 0.9.3"
Gem::Exception: can't activate merb-core (= 0.9.3), already activated merb-core-0.9.2]
from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:319:in `activate'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:65:in `active_gem_with_options'
from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:50:in `gem'
from (irb):6
from /opt/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:61
-
Michael Klishin (antares) May 27th, 2008 @ 03:01 AM
- → State changed from “new” to “invalid”
Jim,
What are your suggestions? Are you sure it is Merb issue and not RubyGems or your environment? Please be more verbose.
-
Jim May 27th, 2008 @ 03:45 AM
Sorry about the terse post. Lighthouse, being the lovely app that it is, lost my data when it died on update. And I was in a hurry at the time.
My suggestion is too find the cause of the problem. Gems versioning appears to be working fine, because merb-core did in fact load the requested version 0.9.2. But something somewhere tried to load 0.9.3. Nothing in my old project would do that, as the test case above tried to show.
Its pretty simple to recreate:
sudo gem uninstall merb 0.9.3
- assuming 0.9.2 is installed
merb-gen newproject
sdo gem install merb
cd newproject
merb 0.9.2
-
Michael Klishin (antares) May 27th, 2008 @ 03:53 AM
- → State changed from “invalid” to “open”
I need to have a closer look. What ORM and templating engines (or other plugins) you use?
Even if it has something to do with Merb, I doubt pre-1.0 versions will have any kind of compatibility with each other because Merb is still shaping up.
-
Jim May 27th, 2008 @ 06:47 AM
I'm using Sequel and haml.
I don't understand the compatiblity statement. The whole point of making this work is so you don't have to be compatable, and, you don't have to freeze a project before you upgrade.
-
Michael D. Ivey (ivey) June 12th, 2008 @ 01:36 AM
- → Assigned user changed from “” to “Michael D. Ivey (ivey)”
-
Ahmed El-Daly July 21st, 2008 @ 08:01 PM
- → Tag changed from “” to “gem”
Any update on this? I'm running into that same problem. Thanks.
-
-
-
Michael Klishin (antares) July 22nd, 2008 @ 05:49 AM
merb-freezer rewrite is on the way: seems that nobody likes the way it works right now
-
Michael Klishin (antares) August 2nd, 2008 @ 06:43 PM
- → Milestone changed from “” to “0.9.6”
-
Michael Klishin (antares) September 4th, 2008 @ 11:53 AM
- → Tag changed from “gem” to “freezer gem”
- → Milestone changed from “0.9.6” to “0.9.7”
-
Michael Klishin (antares) September 10th, 2008 @ 04:48 AM
- → Assigned user changed from “Michael D. Ivey (ivey)” to “Michael Klishin (antares)”
- → State changed from “open” to “resolved”
Given going merb bundler effort and that this ticket is pretty old (Merb is moving very fast at this point), I am closing this. We'll try to make bundler smart enough, but to some point it's a RubyGems issue.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
