Closed joncage closed 12 years ago
The require 'settings' line does not work with ruby 1.9. Just committed a fix. Just place your settings.rb in the same directory as bz2redmine. Am 12.07.2012 12:08, schrieb joncage:
I'm getting an error when I try and run the migration:
sudo ruby bz2redmine.rb /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- settings (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from bz2redmine.rb:29:in `<main>'
I've copied the script and the settings into the redmine directory
I've renamed example_settings.rb to settings.rb
For some reason it's not picking up the settings though. Does it have to be run from a specific location? ..or is this a bug?
Reply to this email directly or view it on GitHub: https://github.com/ralli/bz2redmine/issues/8
Still no joy...
/usr/lib/ruby/1.9.1/rubygems.rb:28:in `require': cannot load such file -- rubygems/defaults (LoadError)
from /usr/lib/ruby/1.9.1/rubygems.rb:28:in `<top (required)>'
from <internal:gem_prelude>:1:in `require'
from <internal:gem_prelude>:1:in `<compiled>'
That looks like a rubygems issue. Since I do not now much about your environment, i am not quite shure how to fix this.
Maybe you should try to upgrade to a later version of rubygems using "gem update --system". Your ruby version is not the current (and supported) one. Maybe you should try to upgrade to upgrade your ruby (using homebrew, aptitude, yum or rvm?)
I have been running bz2redmine with gem 1.8.24 (gem --version) and ruby (1.9.3p194) and ruby 1.8.7 (2012-02-08 patchlevel 358).
HtH
Btw. I am using rvm on Ubuntu...
Okay, we nailed it this time; turned out to be an issue with multiple versions of ruby and a few other minor issues after that.
I'm getting an error when I try and run the migration:
I've copied the script and the settings into the redmine directory
I've renamed example_settings.rb to settings.rb
For some reason it's not picking up the settings though. Does it have to be run from a specific location? ..or is this a bug?