After the recent upgrade of imagemagick from 184.108.40.206-1 to 220.127.116.11-1 it's not possible to install the rmagick ruby gem. Running "gem install rmagick" throws an error "Failed to build gem native extension".
The problem has been reported in the rmagick issue tracker:
There you can see full error traces as well as a discussion on the cause of the problem.
The root of the problem seems to be that some of the symbolic links provided by the package have changed name. Specifically, these links are no longer in the package:
They've been instead been renamed to:
I'm not sure of the reason for the change. I think the simplest solution would be if the package provided links with the old names pointing to the correct .so files.
Would there be any problem with this? Should I submit it as an arch or upstream bug? (I'm not sure if this sould be considered a packaging issue).
Upstream (rmagick) needs to improve their imagemagick detection routines.
At one point they seem to be using the correct way to find the library name (i.e. through Magick-config), but then they perform useless checks using hardcoded library names:
checking for InitializeMagick() in -lMagickCore... no checking for InitializeMagick() in -lMagick... no checking for InitializeMagick() in -lMagick++... no
It should use pkg-config