Your message dated Fri, 06 Dec 2013 00:17:05 -0500 with message-id <[email protected]> and subject line Re: Bug#731484: dpkg-shlibdeps: error: no dependency information found for /usr/lib/libstdc++.so.6 has caused the Debian Bug report #731484, regarding dpkg-shlibdeps: error: no dependency information found for /usr/lib/libstdc++.so.6 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.) -- 731484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731484 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg-dev Version: 1.17.3 Severity: normal When building C++ projects using debhelper within an up-to-date sid cowbuilder these days, i often get the following message during dh_shlibdeps: dh_makeshlibs dh_shlibdeps dpkg-shlibdeps: error: no dependency information found for /usr/lib/libstdc++.so.6 (used by debian/wpagui/usr/sbin/wpa_gui) dh_shlibdeps: dpkg-shlibdeps -Tdebian/wpagui.substvars debian/wpagui/usr/sbin/wpa_gui returned exit code 2 (the above is from a rebuild of the wpa package, but it happens with other packages with C++ components as well, like enigmail). I suspect something bad is happening (possibly due to the cowbuilder environment?), but i don't know how i should investigate further. If you'd like me to test anything, please let me know. Thanks for maintaining dpkg-dev. It's critical infrastructure for me. Regards, --dkg -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/1 CPU core) 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 dpkg-dev depends on: ii base-files 7.2 ii binutils 2.24-1 ii bzip2 1.0.6-5 ii libdpkg-perl 1.17.3 ii make 3.81-8.3 ii patch 2.7.1-4 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages dpkg-dev recommends: ii build-essential 11.6 ii fakeroot 1.20-3 ii gcc [c-compiler] 4:4.8.1-3 ii gcc-4.4 [c-compiler] 4.4.7-5 ii gcc-4.5 [c-compiler] 4.5.4-1 ii gcc-4.6 [c-compiler] 4.6.4-5 ii gcc-4.7 [c-compiler] 4.7.3-9 ii gcc-4.8 [c-compiler] 4.8.2-8 ii gnupg 1.4.15-1.1 ii gpgv 1.4.15-1.1 ii libalgorithm-merge-perl 0.08-2 Versions of packages dpkg-dev suggests: pn debian-keyring <none> -- no debconf information
--- End Message ---
--- Begin Message ---On 12/05/2013 04:59 PM, Sven Joachim wrote: > On 2013-12-05 22:20 +0100, Daniel Kahn Gillmor wrote: > >> Package: dpkg-dev >> Version: 1.17.3 >> Severity: normal >> >> When building C++ projects using debhelper within an up-to-date sid >> cowbuilder these days, i often get the following message during >> dh_shlibdeps: >> >> dh_makeshlibs >> dh_shlibdeps >> dpkg-shlibdeps: error: no dependency information found for >> /usr/lib/libstdc++.so.6 (used by debian/wpagui/usr/sbin/wpa_gui) >> dh_shlibdeps: dpkg-shlibdeps -Tdebian/wpagui.substvars >> debian/wpagui/usr/sbin/wpa_gui returned exit code 2 >> >> (the above is from a rebuild of the wpa package, but it happens with >> other packages with C++ components as well, like enigmail). >> >> I suspect something bad is happening (possibly due to the cowbuilder >> environment?), but i don't know how i should investigate further. If >> you'd like me to test anything, please let me know. > > The /usr/lib/libstdc++.so.6 file should not be there I suppose. There > is no package in unstable that ships it, so it's no wonder that > dpkg-shlibdeps fails to find dependency information for it. sigh. of course, this is right. sorry i didn't catch it myself. i guess this cruft was leftover since the transition of the cowbuilder root to multiarch (years ago?) and somehow propagated along since then. after removing it (and one other library in the same situation), i'm able to build the packages without errors. thanks for the helpful diagnostics, and sorry for the noise, --dkg
signature.asc
Description: OpenPGP digital signature
--- End Message ---
