Package: src:graphicsmagick Version: 1.3.12-1.1+b2 Severity: serious <-- snip -->
# apt-get install libgraphicsmagick3 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libjbig0 Suggested packages: graphicsmagick-dbg The following NEW packages will be installed: libjbig0 The following packages will be upgraded: libgraphicsmagick3 1 upgraded, 1 newly installed, 0 to remove and 103 not upgraded. Need to get 0 B/1,324 kB of archives. After this operation, 61.4 kB of additional disk space will be used. Do you want to continue [Y/n]? Reading changelogs... Done apt-listchanges: Do you want to continue? [Y/n] Selecting previously unselected package libjbig0:amd64. (Reading database ... 321933 files and directories currently installed.) Unpacking libjbig0:amd64 (from .../libjbig0_2.0-2_amd64.deb) ... Preparing to replace libgraphicsmagick3 1.3.12-1.1+b1 (using .../libgraphicsmagick3_1.3.12-1.1+b2_amd64.deb) ... Unpacking replacement libgraphicsmagick3 ... Setting up libjbig0:amd64 (2.0-2) ... Setting up libgraphicsmagick3 (1.3.12-1.1+b2) ... # <-- snip --> It is evil that a binary-only upload changes the list of features enabled in graphicsmagick, and a possible source for serious breakages in post-release security updates. Currently libjbig-dev is being pulled in indirectly through libtiff4-dev. That is not guaranteed to always be the case. Please either add a proper build dependency for jbig support (preferred) or configure graphicsmagick with --without-jbig (in the unlikely case that this is better for some reason). Please also double-check that proper build dependencies or explicit feature disabling are present for all other optional features checked for during configure. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
