Bug#788300: recoverjpeg: Update to 2.3-2 requires replacing imagemagick with graphicsmagick.
David Evensky
evensky at gmail.com
Wed Jun 10 01:33:15 UTC 2015
Package: recoverjpeg
Version: 2.3-2
Severity: normal
Dear Maintainer,
I'm holding up on updating recoverjpeg because it wants to whack imagemagick
and replace with the the graphicsmagick fork. I don't see anything that states
that imagemagick is deprecated, or some feature of graphicsmagick is driving
the change. It is unexpected that this would be required.
Thanks for your response.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages recoverjpeg depends on:
ii exif 0.6.21-1
pn graphicsmagick-imagemagick-compat <none>
ii libc6 2.19-18
ii libgcc1 1:5.1.1-9
ii libstdc++6 5.1.1-9
ii python 2.7.9-1
recoverjpeg recommends no packages.
recoverjpeg suggests no packages.
-- no debconf information
More information about the forensics-devel
mailing list