Upgrade from 2.1.3 to 2.3.1
Replies (2)
RE: Upgrade from 2.1.3 to 2.3.1
-
Added by Toshi MARUYAMA over 11 years ago
You have plugin which defines capybara in Gemfile.
Upgrade plugin.
RE: Upgrade from 2.1.3 to 2.3.1
-
Added by Prasanth Kumar over 11 years ago
This marks that the installation have gem specification twice or more times.
On unix environment traverse through the Redmine DocRoot and give the command "egrep -irn capybara *" this will display the lines matching the word capybara... keep the least version declaration and comment the one with latest. This should solve the problem.
/Prasanth Kumar
Tk Tz wrote:
Hello there,
I am facing the problem with redmine upgrade from 2.1.3 to 2.3.1.
The main problem is, that I am not able to generate secret_token.rb via the command rake generate_secret_token.
Still getting this message
"
You cannot specify the same gem twice with different version requirements.
You specified: capybara (~> 2.0.0) and capybara (>= 0)
"It doesnt works even I update to capybara version 2.1.0 !!
And my question is: Is it possible to copy secret_token.rb from OLD (2.1.3) version to NEW (2.3.1) version ? And continue with installation steps as it is mentioned in http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade ?
Thanks for answers.
Regards Tk Tz