On Fri, 25 Feb 2022, László Böszörményi (GCS) wrote:
On Fri, Feb 25, 2022 at 4:35 PM Bob Friesenhahn
<bfrie...@simple.dallas.tx.us> wrote:
On Fri, 25 Feb 2022, László Böszörményi (GCS) wrote:
Wild guess only, as I'm away from home right now. But that image can
be exif.jpg [1] or any other from the 'fixtures' directory.
[1]
https://salsa.debian.org/ruby-team/ruby-mini-magick/-/blob/master/spec/fixtures/exif.jpg
This is what I get from 'gm identify -verbose exif.jpg' for the above
file on my system. Is the output different/failing on the targets
with the problem?
This should be it. Is your GM the latest version from Mercurial?
Yes it is.
Image: /home/bfriesen/src/minimagick.git/spec/fixtures/exif.jpg
Exif Version: 0220
Date Time Original: 2016:11:12 09:17:56
Flash: 0
Package ruby-mini-magick check tree values: EXIF:Flash,
DateTimeOriginal and ExifVersion. With GM 1.3.37 it succeeds and gets
real values in order 0, a string and 0220 just like in your dump. But
with the mentioned GM commit the results are in order "", nil and nil.
Maybe the GM output or its variable types changed somehow and now
ruby-mini-magick can't parse that? Needs more investigation. I think
tomorrow in the evening (CET) I will arrive back home and will try to
support you with more details.
There is dependency on the JPEG library so some change in the JPEG
library could impact code which works "fine" on some other system.
I am using Ubuntu 20.04 LTS and the JPEG that comes with that OS.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
