clone 320029 -1
reassign -1 libmagick6 6:6.2.3.3-1
thanks
Hadmut Danisch wrote:
Yup, what you're seeing is a binary-compatibility conflict between
librmagick-ruby1.8_1.6.0-1 (which was built against ImageMagick-6.0.6),
and the newer ImageMagick-6.2.x libraries.
BTW:
Isn't this an error of t
On Wed, Jul 27, 2005 at 09:43:00PM +1000, Mike Williams wrote:
>
> Yup, what you're seeing is a binary-compatibility conflict between
> librmagick-ruby1.8_1.6.0-1 (which was built against ImageMagick-6.0.6),
> and the newer ImageMagick-6.2.x libraries.
BTW:
Isn't this an error of the ImageMag
Hadmut Danisch wrote:
On the system where the bug occurs:
ii libmagick66:6.2.3.3-1...
Just for comparison my home system, where the bug does not occur:
ii libmagick6 6:6.0.6.2-1.6 ...
So interestingly, the system with the bug is actually on a
newer leve
On Wed, Jul 27, 2005 at 08:19:45PM +1000, Mike Williams wrote:
>
> What versions of libmagick6 and librmagick-ruby1.8 are you running??
I had the problem on my workstation at work and don't want to
send emails from that machine, that's why I didn't use
reportbug.
On the system where the bug o
[EMAIL PROTECTED] wrote:
Magick::Image.read always chops the first 8 characters of the
filename.
I've seen this happen before, when Imagemagick was upgraded without a
corresponding rebuild of librmagick-ruby.
What versions of libmagick6 and librmagick-ruby1.8 are you running??
Normally, if
Package: librmagick-ruby1.8
Version: 1.6.0-1
There's something wrong with character pointers:
% ruby -r RMagick -e 'Magick::Image.read("testimage.png")'
-e:1:in `read': unable to open image `e.png': No such file or
directory: (Magick::ImageMagickError)
from -e:1
Magick::Image.read alwa
6 matches
Mail list logo
