Package: libtiff5
Version: 4.0.3-12.3+deb8u3
Severity: normal

Dear Maintainer,

As of today, we are getting this warning:

  Invalid tag "Predictor" (not supported by codec). (_TIFFVGetField)

* What led up to the situation?

  The upgrade of libtiff5:amd from libtiff5:4.0.3-12.3+deb8u2 to
  4.0.3-12.3+deb8u3 has caused a new warning to be emitted when creating TIFF
  files.

  We know it was this specific package because:

  * our test server logs from yesterday do not include the warning
  * a dist-upgrade this morning upgraded only one package: libtiff5
  * our test server logs today now include the warning
  * the test server is running the same jobs as yesterday
  * we can reproduce the warning with test commands on other servers which
    have been updated but not when using the same commands on servers which
    are still running 4.0.3-12.3+deb8u2

The following two commands create a JPG file (a rectangle of solid color) and
then convert the JPG to a TIFF.  The warning is produced by the second command:

  $ gm convert -size 100x100 xc:#00aaaa rect.jpg
  $ gm convert -colorspace RGB rect.jpg rect.tif
  gm convert: rect.tif: Invalid tag "Predictor" (not supported by codec).
  (_TIFFVGetField).

Both of these commands use the GraphicsMagick 'gm' command but that command is
using libtiff.

Regards
Grant McLean

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_NZ.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libtiff5 depends on:
ii  libc6              2.19-18+deb8u7
ii  libjbig0           2.1-3.1
ii  libjpeg62-turbo    1:1.3.1-12
ii  liblzma5           5.1.1alpha+20120614-2+b3
ii  multiarch-support  2.19-18+deb8u7
ii  zlib1g             1:1.2.8.dfsg-2+b1

libtiff5 recommends no packages.

libtiff5 suggests no packages.

-- no debconf information

Reply via email to