I investigated the bug. Here is a test script : #!/usr/bin/ruby
require 'RMagick'
im = Magick::Image::read('circle-510.png')
The problem is the one described on http://rubyforge.org/forum/forum.php?thread_id=1344&forum_id=33 . It is caused by libmagick6 being "too new" compared to librmagick-ruby. Also, librmagick-ruby doesn't even build currently inside breezy.
I think that the only solution is to backport the new version of librmagick-ruby into breezy. But under which conditions would this be made ? librmagick-ruby isn't used by any package, so this could be made without risking to break everything.
I investigated the bug. Here is a test script :
#!/usr/bin/ruby
require 'RMagick'
im = Magick: :Image: :read(' circle- 510.png' )
The problem is the one described on http:// rubyforge. org/forum/ forum.php? thread_ id=1344& forum_id= 33 . It is caused by libmagick6 being "too new" compared to librmagick-ruby. Also, librmagick-ruby doesn't even build currently inside breezy.
I think that the only solution is to backport the new version of librmagick-ruby into breezy. But under which conditions would this be made ? librmagick-ruby isn't used by any package, so this could be made without risking to break everything.