RedMine Installation: can't activate rubyforge...
Added by Ilya Khanataev about 15 years ago
Hello!
I cannot start the db-migration process and have the same problem like here described:
(11:55:14) [redmine] rake db:migrate RAILS_ENV="production"
(in /my-redmine-path/redmine)
rake aborted!
can't activate rubyforge (= 0.4.5, runtime), already activated rubyforge-1.0.2
Has somebody any ideas?
Thanks.
P.S. My system parameters:
Linux:
Linux version 2.6.27.7-grsec (root@imageneu) (gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r 1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) # 25 SMP Mon Feb 16 16:37:38 CET 2009
Ruby:
ruby 1.8.7p5000 (2009-02-19) [i686-linux]
Rails:
Rails 2.3.2
Replies (2)
RE: RedMine Installation: can't activate rubyforge...
-
Added by Joe Clarke about 15 years ago
I would recommend uninstalling all the versions of rubyforge you have on machine than reinstalling the latest.
gem uninstall rubyforge
gem install rubyforge
RE: RedMine Installation: can't activate rubyforge...
-
Added by Ilya Khanataev about 15 years ago
I cannot do it -- I don't have write permissions into the gems directory:
(20:33:55) [~] gem uninstall rubyforge
Select gem to uninstall:
1. rubyforge-0.4.5
2. rubyforge-1.0.2
3. All versions
1
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions into the /usr/lib/ruby/gems/1.8 directory.
(20:34:04) [~] gem uninstall rubyforge
Select gem to uninstall:
1. rubyforge-0.4.5
2. rubyforge-1.0.2
3. All versions
2
You have requested to uninstall the gem:
rubyforge-1.0.2
hoe-1.5.1 depends on [rubyforge (>= 0.4.4)]
hoe-1.8.3 depends on [rubyforge (>= 1.0.2)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn] Y
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions into the /usr/lib/ruby/gems/1.8 directory.
(20:34:21) [~] gem uninstall rubyforge
Select gem to uninstall:
1. rubyforge-0.4.5
2. rubyforge-1.0.2
3. All versions
3
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions into the /usr/lib/ruby/gems/1.8 directory.