On Tue, Jul 26, 2011 at 08:16:08 +0200, Neil Williams wrote: > notfound 634550 8:6.6.9.7-5 > quit > > Now that libwmf is fixed, imagemagick builds successfully in a clean > pbuilder chroot without changes. Maybe #634550 should have been > re-assigned to libwmf in the first place. > > During the build, there was a hint about #634194 and the possible > reason for the binNMU request: > > /usr/bin/ld: warning: libjpeg.so.62, needed by /usr/lib/libtiff.so, may > conflict with libjpeg.so.8 > > imagemagick in the archive currently depends on libjpeg62 and my > rebuilt version depends on libjpeg8 (but brings in libjpeg62 via > libtiff4): > > Depends: libbz2-1.0, libc6 (>= 2.2.5), libfontconfig1 (>= 2.8.0), > libfreetype6 (>= 2.2.1), libglib2.0-0 (>= 2.12.0), libgomp1 (>= 4.2.1), > libice6 (>= 1:1.0.0), libjpeg8 (>= 8c), liblcms1 (>= 1.15-1), liblqr-1-0 (>= > 0.1.0), libltdl7 (>= 2.4), libmagickcore4 (>= 8:6.6.9.7), libmagickwand4 (>= > 8:6.6.9.7), libsm6, libtiff4, libx11-6, libxext6, libxt6, zlib1g (>= 1:1.1.4) > > (imagemagick-extra has the depends on libwmf) > > Would the best solution here be to binNMU libtiff to close #634194 and > then reassign #634550 for an imagemagick binNMU? > No. It seems like the best solution is to close those spurious bugs.
Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
