Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 activate rspec (= 1.1.12, runtime), already activated rspec-1.2.6 I found that uninstalling all rspec versions greater than 1.1.12 made the problem go away. Actually, is there any way to solve this problem other than uninstalling all versions other than 1.1.12? I would like to play with the current developments of rspec (since I just bought the rspec book) but my reliance on Radiant is more... I agree that un-installing more recent versions of rspec seems like a drastic measure, but it was the only thing I tried that would work. Prior to that, I tried each of the following without success: * Adding the line: config.gem rspec, :version = 1.1.12 to the environment * Unpacking rspec-1.1.12 into vendor/gems/ It was only necessary to uninstall rspec so that I could run the task `rake radiant:update`. Once this task had run, I found that I could re- install the most recent version of rspec (currently 1.2.6), and it didn't seem to cause any further conflict. Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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: can't activate rspec (= 1.1.12, runtime), already activated rspec-1.2.6 I found that uninstalling all rspec versions greater than 1.1.12 made the problem go away. Actually, is there any way to solve this problem other than uninstalling all versions other than 1.1.12? I would like to play with the current developments of rspec (since I just bought the rspec book) but my reliance on Radiant is more... I agree that un-installing more recent versions of rspec seems like a drastic measure, but it was the only thing I tried that would work. Prior to that, I tried each of the following without success: * Adding the line: config.gem rspec, :version = 1.1.12 to the environment * Unpacking rspec-1.1.12 into vendor/gems/ It was only necessary to uninstall rspec so that I could run the task `rake radiant:update`. Once this task had run, I found that I could re-install the most recent version of rspec (currently 1.2.6), and it didn't seem to cause any further conflict. That's interesting - I got the already activated... error when I did script/server -e production -p 3700 Hmm... Cheers, Mohit. 5/28/2009 | 4:57 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 is 1.1.12, but what is the required version of rspec_rails? You could likely do the same in your project (and not the gem). I already tried that, but I think I see now where my mistake was: I tried unpacking the rspec gem into vendor/gems (seeing as it's a gem), when I should have unpacked it to vendor/plugins. I'm sorry this is causing so much pain - it was my fault for not locking the gem version properly. I realise that Radiant edge is now up at version 0.8.0, but I wonder whether it might be worth releasing a version 0.7.2 which could address this issue? Thanks, Drew Mohit Sindhwani wrote: 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: can't activate rspec (= 1.1.12, runtime), already activated rspec-1.2.6 I found that uninstalling all rspec versions greater than 1.1.12 made the problem go away. Actually, is there any way to solve this problem other than uninstalling all versions other than 1.1.12? I would like to play with the current developments of rspec (since I just bought the rspec book) but my reliance on Radiant is more... I agree that un-installing more recent versions of rspec seems like a drastic measure, but it was the only thing I tried that would work. Prior to that, I tried each of the following without success: * Adding the line: config.gem rspec, :version = 1.1.12 to the environment * Unpacking rspec-1.1.12 into vendor/gems/ It was only necessary to uninstall rspec so that I could run the task `rake radiant:update`. Once this task had run, I found that I could re-install the most recent version of rspec (currently 1.2.6), and it didn't seem to cause any further conflict. That's interesting - I got the already activated... error when I did script/server -e production -p 3700 Hmm... Cheers, Mohit. 5/28/2009 | 4:57 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 always equal. I realise that Radiant edge is now up at version 0.8.0, but I wonder whether it might be worth releasing a version 0.7.2 which could address this issue? I may have to go back and create a branch to accomplish that, and backport some bugfixes from edge. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 rspec versions greater than 1.1.12 made the problem go away. Once I had uninstalled more recent versions of rspec, I could run `rake radiant:update` fine. After running the rake task, I found that I could reinstall the most recent version of rspec (currently 1.2.6), and it no longer conflicted with Radiant. So it seems like there was just some catch-22 requirement going on within the `rake radiant:update` task. I ran into a couple of other problems in trying to upgrade from 0.6.9 to 0.7.1, so I wrote them up and put a new page on the wiki. Check it out: http://wiki.github.com/radiant/radiant/updating-a-site-from-radiant-069-to-071 I hope this will save others some time when they come to do the same. Cheers, Drew On 22 Apr 2009, at 10:17, Jeffrey Jones wrote: Yes, Radiant 0.7.1 Rspec only works with 1.1.12 and, from my experience, merely having Rspec 1.2.x installed totally FUBARs Rspec 1.1.12. There is a bug on the rspec tracker mentioning this but no movement on it yet. https://rhomobile.lighthouseapp.com/projects/16701/tickets/144-cant-activate-rspec-1112-runtime-already-activated-rspec-120 I have no solution or workaround for this issue. Jeff Enrico Teotti wrote: 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 to change something in the radiant project, and rake spec returns: http://pastie.org/454312 Only after removing rspec (and rspec-rails) 1.2.2 1.2.4 my test are running fine again. Any clue why? RubyGem version error: rspec(1.1.11 not = 1.2.4) (Gem::LoadError) doesn't look good to me :-\ Is anybody running the same versions or radiant and rspec? Cheers, Enrico ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 uninstalling all rspec versions greater than 1.1.12 made the problem go away. Yes, I just noticed this when I installed a new version of rspec. Once I had uninstalled more recent versions of rspec, I could run `rake radiant:update` fine. After running the rake task, I found that I could reinstall the most recent version of rspec (currently 1.2.6), and it no longer conflicted with Radiant. So it seems like there was just some catch-22 requirement going on within the `rake radiant:update` task. I ran into a couple of other problems in trying to upgrade from 0.6.9 to 0.7.1, so I wrote them up and put a new page on the wiki. Check it out: http://wiki.github.com/radiant/radiant/updating-a-site-from-radiant-069-to-071 I hope this will save others some time when they come to do the same. Thanks a lot! It is a nice list. Cheers, Mohit. 5/28/2009 | 12:10 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 rspec-1.2.6 I found that uninstalling all rspec versions greater than 1.1.12 made the problem go away. Actually, is there any way to solve this problem other than uninstalling all versions other than 1.1.12? I would like to play with the current developments of rspec (since I just bought the rspec book) but my reliance on Radiant is more... Cheers, Mohit. 5/28/2009 | 12:20 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 to change something in the radiant project, and rake spec returns: http://pastie.org/454312 Only after removing rspec (and rspec-rails) 1.2.2 1.2.4 my test are running fine again. Any clue why? RubyGem version error: rspec(1.1.11 not = 1.2.4) (Gem::LoadError) doesn't look good to me :-\ Is anybody running the same versions or radiant and rspec? Cheers, Enrico ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rspec 1.2.2 | radiant 0.7.1 anybody?
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 Sean, Just to let you know that, as far as I can tell, you are off the hook on this one as even when I use config.gem to try and make radiant use 1.1.12 it still gurgles and dies with an error trying to activate 1.2.x I think it is a general rspec failure rather than anything Radiant specific. Jeff Sean Cribbs wrote: My apologies - I should have linked Radiant to a specific version of RSpec. Going forward, we will be doing that and constraining the activated version with config.gem. Part of the reason I switched to Cucumber in edge (besides its raw AWESOMENESS) is because RSpec 1.2 broke spec_integration. Sean Jeffrey Jones wrote: Yes, Radiant 0.7.1 Rspec only works with 1.1.12 and, from my experience, merely having Rspec 1.2.x installed totally FUBARs Rspec 1.1.12. There is a bug on the rspec tracker mentioning this but no movement on it yet. https://rhomobile.lighthouseapp.com/projects/16701/tickets/144-cant-activate-rspec-1112-runtime-already-activated-rspec-120 I have no solution or workaround for this issue. Jeff Enrico Teotti wrote: 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 to change something in the radiant project, and rake spec returns: http://pastie.org/454312 Only after removing rspec (and rspec-rails) 1.2.2 1.2.4 my test are running fine again. Any clue why? RubyGem version error: rspec(1.1.11 not = 1.2.4) (Gem::LoadError) doesn't look good to me :-\ Is anybody running the same versions or radiant and rspec? Cheers, Enrico ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
