Defect #6017
closed
"This installation of RMagick was configured with ImageMagick 6.5.5 but ImageMagick 6.5.7-8 is in use"
0%
Description
I installed redmine on an ubuntu 10.04 box. I got all the ruby 1.8 from the ubuntu packages (with the usual aptitude installs) including (librmagick-ruby1.8 2.11.1-1) and installed rails 2.3.5 via a sudo gem install and installed Redmine from svn trunk (r3902 at the time)
The error:
When I came to the "rake db:migrate" step, I got the this error crashing the command:
"This installation of RMagick was configured with ImageMagick 6.5.5 but ImageMagick 6.5.7-8 is in use"
I googled around and found a debian thread saying that I can bypass this RMagick check and that it wasn't so big a deal (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557778)
So I added that bypass line to lib/redmine.rb (see attached patch to this issue ticket) and the rake db:migrate went through as did the rest of the installation.
Is the bypass a good idea in general? If so is that really the best place to put it? I leave it in greater ruby hands to answer.
Thanks!
Yuval
Files
Updated by Felix Schäfer over 13 years ago
- Status changed from New to Closed
- Resolution set to Invalid
This is an ubuntu specific problem, and one with a gem, not redmine, please contact the ubuntu maintainers if you think this is a bug.
The error you are seeing though is that RMagick (the ruby gem for imagemagick) has been compiled against another version of ImageMagick than the one you have installed on your system, and that it can't work with it. If your RMagick really comes from apt, then this is a bug in the package that it doesn't force pull the exact ImageMagick version it has been compiled against.
Regarding the patch: use at your own risk, but I think the worst that could happen is somewhat funky graphs in the repository section.
Updated by Yuval Maman over 13 years ago
This makes sense that it's a conflict between packaged software requirements (RMagick library) and the package requirements (RMagick deb package). I'll redirect to there.
Thanks, Felix
Updated by Yuval Maman over 13 years ago
And today,
I just noticed that the debian community did in fact release a fix for it and the ubuntu community is going to get one up soon. For those wanting to track that:
https://bugs.launchpad.net/ubuntu/+source/librmagick-ruby/+bug/518122
Yuval