Your message dated Sat, 4 Jun 2011 14:48:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#629182: dpkg-shlibbdeps throws an invalid warning when
a program depends on gtk+
has caused the Debian Bug report #629182,
regarding dpkg-shlibbdeps throws an invalid warning when a program depends on
gtk+
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.)
--
629182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.16.0.3
Severity: normal
My application [1] depends on gtk+-2.0 and -pthread seems to be brought in by
this:
$ pkg-config --cflags gtk+-2.0
-pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2
-I/usr/include/libpng12
This seems to make dpkg-shlibdeps throw a warning [2], which I'd consider to be
invalid.
[1] - http://packages.debian.org/sid/clipit
[2] - dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided
if "debian/clipit/usr/bin/clipit" were not uselessly linked against it (they
use none of its symbols).
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages dpkg-dev depends on:
ii base-files 6.3 Debian base system miscellaneous f
ii binutils 2.21.51.20110523-1 The GNU assembler, linker and bina
ii bzip2 1.0.5-6 high-quality block-sorting file co
ii libdpkg-perl 1.16.0.3 Dpkg perl modules
ii make 3.81-8.1 An utility for Directing compilati
ii patch 2.6.1-2 Apply a diff file to an original
ii xz-utils 5.0.0-2 XZ-format compression utilities
Versions of packages dpkg-dev recommends:
ii build-essential 11.5 Informational list of build-essent
ii fakeroot 1.15.1-1 tool for simulating superuser priv
ii gcc [c-compiler] 4:4.5.2-2 The GNU C compiler
ii gcc-4.4 [c-compiler] 4.4.6-3 The GNU C compiler
ii gcc-4.5 [c-compiler] 4.5.3-1 The GNU C compiler
ii gnupg 1.4.11-3 GNU privacy guard - a free PGP rep
ii gpgv 1.4.11-3 GNU privacy guard - signature veri
pn libalgorithm-merge-perl <none> (no description available)
Versions of packages dpkg-dev suggests:
ii debian-keyring 2011.03.03 GnuPG keys of Debian Developers
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 04 Jun 2011, Cristian Henzel wrote:
> > dpkg-shlibdeps already has options so that you can exclude the warnings
> > that you want to ignore... I don't really see what you expect in response
> > to your bug report.
>
> Well, my package doesn't actually depend on -pthread to work correctly, but I
> am
> not aware of a possibility to tell pkg-config to not pull in that dependency.
> If
> that is possible, it's a mistake on my part, but if not I wouldn't consider it
> necessary for dpkg-shlibdeps to throw a warning for that.
> If you don't consider this a proper bug you could mark it as wishlist or even
> close it.
Well, dpkg-shlibdeps has no knowledge of pkg-config or any build options.
It sees binaries using symbols and libraries.
And it sees that none of the symbols of libpthread are used by your binary
and that it's thus not required. The warning is correct even if it's
not practical for you to fix it.
So I'm closing the bug.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--- End Message ---
