I’ve already asked about this on
but am bringing my troubles here as Jeremy K. requested today.
After upgrading my gem rails to the 2.0 preview release (184.108.40.20694
was the first one I got) I tried creating a new project and installing
the acts_as_attachment plugin. Then I ran rake test:plugins to make
sure everything is compatible before proceeding with my work and I got
errors like this:
rubygems.rb:246:in `activate’: can’t activate rails (= 1.2.4),
already activated rails-220.127.116.1194] (Gem::Exception)
A similar error occurs with acts_as_paranoid, though it complains
about one of the “active” gems rather than the rails gem itself.
Today I freshened my gems and installed 18.104.22.16819. I repeated the
steps above and got an equivalent error:
… can’t activate rails (= 1.2.5), already activated
I’d already tried freezing rails in various ways and I’ve messed with
RAILS_GEM_VERSION, both without success.
Today I tried gem cleanup rails, which left me with just 22.214.171.12419
instead of the six or seven versions I had previously. I created a new
project etc., as above, and when I ran rake test\plugins this time it
failed slightly differently:
gem_original_require': no such file to load -- breakpoint (MissingSourceFile) from [...]/ruby/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:inrequire’
Can anyone offer any help with this?