On 28 May 2009, at 05:20, Mohit Sindhwani wrote:
Mohit Sindhwani wrote:
Andrew Neil wrote:
I've just ran into this problem too, whilst trying to upgrade a
site from Radiant 0.6.9 to 0.7.1. I found that I could not run
`rake radiant:update`. I kept getting a message like:
can't
Andrew Neil wrote:
On 28 May 2009, at 05:20, Mohit Sindhwani wrote:
Mohit Sindhwani wrote:
Andrew Neil wrote:
I've just ran into this problem too, whilst trying to upgrade a
site from Radiant 0.6.9 to 0.7.1. I found that I could not run
`rake radiant:update`. I kept getting a message like:
On 28 May 2009, at 15:10, Sean Cribbs wrote:
The solution I came up with was to go into the gem and unpack rspec
and rspec rails into vendor/plugins.
So you actually unpacked rspec and rspec_rails into the vendor/plugins
directory of the radiant-0.7.1 gem?
The required version of rspec
So you actually unpacked rspec and rspec_rails into the vendor/plugins
directory of the radiant-0.7.1 gem?
The required version of rspec is 1.1.12, but what is the required
version of rspec_rails?
Yes, that's where I unpacked them. The version numbers on rspec and
rspec-rails are
I've just ran into this problem too, whilst trying to upgrade a site
from Radiant 0.6.9 to 0.7.1. I found that I could not run `rake
radiant:update`. I kept getting a message like:
can't activate rspec (= 1.1.12, runtime), already activated rspec-1.2.6
I found that uninstalling all
Andrew Neil wrote:
I've just ran into this problem too, whilst trying to upgrade a site
from Radiant 0.6.9 to 0.7.1. I found that I could not run `rake
radiant:update`. I kept getting a message like:
can't activate rspec (= 1.1.12, runtime), already activated
rspec-1.2.6
I found that
Mohit Sindhwani wrote:
Andrew Neil wrote:
I've just ran into this problem too, whilst trying to upgrade a site
from Radiant 0.6.9 to 0.7.1. I found that I could not run `rake
radiant:update`. I kept getting a message like:
can't activate rspec (= 1.1.12, runtime), already activated
Hi,
I was happily running my test suite (rspec+cucumber) in my radiant extension.
I've frozen the rspec gems inside /vendor/gems
rspec-1.1.12rspec-rails-1.1.12
I've deployed that project, and started to work on some other rails
project and installed rspec 1.2.2 and 1.2.4.
Today I had
Jeff,
That may be so, but I've successfully used config.gem in other projects
to lock to specific versions of gems, including RSpec. IIRC there was a
bug in the original implementation of config.gem that was fixed in Rails
2.3. I guess we'll wait and see!
Sean
Jeffrey Jones wrote:
Ahoi
