Your message dated Tue, 07 Oct 2014 10:01:43 -0400
with message-id <[email protected]>
and subject line Re: Bug#764217: ld: warning: libjpeg.so.62, needed by
libtiff.so, may conflict with libjpeg.so.8
has caused the Debian Bug report #764217,
regarding ld: warning: libjpeg.so.62, needed by libtiff.so, may conflict with
libjpeg.so.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
764217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764217
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libtiff5
Version: 4.0.3-10+b1
Severity: wishlist
Dear Maintainer,
I'm linking libtiff.so to the program, that is linked to the libjpeg.so.8,
and this causes following message:
/usr/bin/ld: warning: libjpeg.so.62, needed by
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libtiff.so, may
conflict with libjpeg.so.8
Please rebuild libtiff5 against libjpeg8
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libtiff5 depends on:
ii libc6 2.19-11
ii libjbig0 2.1-3
ii libjpeg62 1:1.3.1-4
ii liblzma5 5.1.1alpha+20120614-2
ii multiarch-support 2.19-11
ii zlib1g 1:1.2.8.dfsg-2
libtiff5 recommends no packages.
libtiff5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
"David Ronnenberg" <[email protected]> wrote:
> Dear Maintainer and followers,
>
> I can confirm this bug in Jessie.
>
> Furthermore dependencies in other versions seem to be messy: on Sid
> libtiff5 depends on libjpeg62 and libjpeg8. Whereas libtiff4 (not
> available in Jessie) in Sid and Wheezy depend on libjpeg8.
>
> https://packages.debian.org/sid/libtiff5
> https://packages.debian.org/sid/libtiff4
> https://packages.debian.org/wheezy/libtiff4
I'm confused about what's going on here, actually. The tiff packages
(both the removed tiff3 package and current tiff package) specify
libjpeg-dev as the build dependency. This is supposed to result in a
dependency on whichever jpeg version is considered the best one to use
for packages that don't have a specific reason to need a particular
version. Right now it seems that libjpeg-dev is provided by
libjpeg62-dev rather than libjpeg8-dev, which is not at all what I would
have expected.
On my sid system, running ldd over both the i386 version and the x86_64
version of libtiff.so.5 show that it linked with libjpeg.so.8. While the
x86_64 version of libtiff is the one I built in my clean pbuilder
chroot, the i386 one on my system was built by a buildd. Okay, looking
more closely, I still have 4.0.3-10 on my system, but I see that
4.0.3-10+b1 depends on libjpeg62, so this happened after the last binary
NMU. There must be a transition going on.
Here it is: https://release.debian.org/transitions/html/jpeg-turbo.html
So basically it looks like you're just seeing chaos because we're in the
middle of a transition to libjpeg-turbo, and the tiff packages are doing
exactly what they're supposed to: depending on libjpeg-dev so they get
the intended version.
--
Jay Berkenbilt <[email protected]>
--- End Message ---
