Your message dated Tue, 07 Feb 2006 14:26:29 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#351743: dpkg-shlibdeps now generates warnings for usage that previously worked has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message --->From [EMAIL PROTECTED] Mon Feb 06 21:13:00 2006 Received: (at submit) by bugs.debian.org; 7 Feb 2006 05:13:00 +0000 Return-path: <[EMAIL PROTECTED]> Received: from pollock.hmdnsgroup.com ([63.247.129.26]) by spohr.debian.org with esmtp (Exim 4.50) id 1F6L9v-00087x-T1 for [EMAIL PROTECTED]; Mon, 06 Feb 2006 21:13:00 -0800 Received: from dsl027-161-197.atl1.dsl.speakeasy.net ([216.27.161.197]:38551 helo=case.local) by pollock.hmdnsgroup.com with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.52) id 1F6L9u-0003C8-Db for [EMAIL PROTECTED]; Tue, 07 Feb 2006 00:12:59 -0500 Subject: dpkg-shlibdeps now generates warnings for usage that previously worked From: Barry Hawkins <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ppNmF9QGEV/DGfCsScEr" Organization: All Things Computed Date: Tue, 07 Feb 2006 00:12:51 -0500 Message-Id: <[EMAIL PROTECTED]> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-HMDNSGroup-MailScanner-Information: Please contact the ISP for more information X-HMDNSGroup-MailScanner: Found to be clean X-HMDNSGroup-MailScanner-SpamCheck: X-HMDNSGroup-MailScanner-From: [EMAIL PROTECTED] X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - pollock.hmdnsgroup.com X-AntiAbuse: Original Domain - bugs.debian.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alltc.com X-Source: X-Source-Args: X-Source-Dir: Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 --=-ppNmF9QGEV/DGfCsScEr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Package: dpkg-dev Version: 1.13.13 Severity: normal First, thank you very much for your work in Debian at large and dpkg-dev. In java-package, we make use of dh_shlibdeps in the rules file we generated when packaging JREs and JDKs using the make-jpkg command. Version 0.27 is the current version of java-package in unstable and testing. Prior to the upgrade of dpkg-dev, our invocation of dh_shlibdeps worked without issue. Now, it generates warnings for each .so that it finds in the directories passed to the -l command option of dh_shlibdeps: We first perform a find to enumerate the directories containing libraries: [...] ldpath=3D for dir in $( find "$install_dir" -type f -name "*.so*" -printf "%h\n" | sort -u ); do if [[ -z "$ldpath" ]]; then ldpath=3D"$dir" else ldpath=3D"$ldpath:$dir" fi done [...] This produces a colon-delimited list of the directories to be passed to dh_shlibdeps -l parameter. As an example, I have captured the output of that command for the root directory of the Sun Java(TM) 1.5 JDK Update 06: /home/barryh/jdk1.5.0_06/demo/jvmti/gctest/lib:/home/barryh/jdk1.5.0_06/dem= o/jvmti/heapTracker/lib:/home/barryh/jdk1.5.0_06/demo/jvmti/heapViewer/lib:= /home/barryh/jdk1.5.0_06/demo/jvmti/mtrace/lib:/home/barryh/jdk1.5.0_06/dem= o/jvmti/versionCheck/lib:/home/barryh/jdk1.5.0_06/demo/jvmti/waiters/lib:/h= ome/barryh/jdk1.5.0_06/jre/lib/i386:/home/barryh/jdk1.5.0_06/jre/lib/i386/c= lient:/home/barryh/jdk1.5.0_06/jre/lib/i386/headless:/home/barryh/jdk1.5.0_= 06/jre/lib/i386/motif21:/home/barryh/jdk1.5.0_06/jre/lib/i386/native_thread= s:/home/barryh/jdk1.5.0_06/jre/lib/i386/server:/home/barryh/jdk1.5.0_06/jre= /lib/i386/xawt:/home/barryh/jdk1.5.0_06/jre/plugin/i386/ns7:/home/barryh/jd= k1.5.0_06/jre/plugin/i386/ns7-gcc29 Passing this to dh_shlibdeps results in the following litany of warnings: [...] dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libverify.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libnet.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libmlib_image.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libmlib_image.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libawt.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libmlib_image.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libawt.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libmlib_image.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libawt.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libawt.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libodbcinst.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libodbc.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libawt.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libmawt.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjvm.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava_crw_demo.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava_crw_demo_g.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava_crw_demo.so' not recognized dpkg-shlibdeps: warning: format of `NEEDED libjava_crw_demo_g.so' not recognized [...] Prior to the upgrade of dpkg-dev, this usage of dh_shlibdeps issued no warnings. Could you guys provide some insight as to whether or not this is a bug and how we can adjust our usage of dh_shlibdeps to avoid these warnings? The use of dh_makeshlibs as mentioned in the dh_shlibdebps causes no change in behavior. Regards, --=20 Barry Hawkins All Things Computed site: www.alltc.com weblog: www.yepthatsme.com Registered Linux User #368650 --=-ppNmF9QGEV/DGfCsScEr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD6CxTHuKcDICy0QoRAsvqAJ0bNCP7g72Rm5RsmvdjkVs3Lx6+5wCgw64G Sy48Bg+sw7kMSK2asGMVgOg= =DP3J -----END PGP SIGNATURE----- --=-ppNmF9QGEV/DGfCsScEr--
--- End Message ---
--- Begin Message --->From [EMAIL PROTECTED] Tue Feb 07 11:26:37 2006 Received: (at 351743-done) by bugs.debian.org; 7 Feb 2006 19:26:37 +0000 Return-path: <[EMAIL PROTECTED]> Received: from pollock.hmdnsgroup.com ([63.247.129.26]) by spohr.debian.org with esmtp (Exim 4.50) id 1F6YU1-00070p-CJ; Tue, 07 Feb 2006 11:26:37 -0800 Received: from dsl027-161-197.atl1.dsl.speakeasy.net ([216.27.161.197]:56503 helo=case.local) by pollock.hmdnsgroup.com with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.52) id 1F6YTy-0001Qt-Fr; Tue, 07 Feb 2006 14:26:34 -0500 Subject: Re: Bug#351743: dpkg-shlibdeps now generates warnings for usage that previously worked From: Barry Hawkins <[EMAIL PROTECTED]> To: Frank Lichtenheld <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Y0Ad2YZDqJLKep21a/dr" Organization: All Things Computed Date: Tue, 07 Feb 2006 14:26:29 -0500 Message-Id: <[EMAIL PROTECTED]> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-HMDNSGroup-MailScanner-Information: Please contact the ISP for more information X-HMDNSGroup-MailScanner: Found to be clean X-HMDNSGroup-MailScanner-SpamCheck: X-HMDNSGroup-MailScanner-From: [EMAIL PROTECTED] X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - pollock.hmdnsgroup.com X-AntiAbuse: Original Domain - bugs.debian.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alltc.com X-Source: X-Source-Args: X-Source-Dir: X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_BUG_NUMBER, VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2005_01_02 --=-Y0Ad2YZDqJLKep21a/dr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable reassign 351743 dpkg-dev stop On Tue, 2006-02-07 at 16:04 +0100, Frank Lichtenheld wrote: [...] > > Prior to the upgrade of dpkg-dev, this usage of dh_shlibdeps issued no > > warnings. Could you guys provide some insight as to whether or not thi= s > > is a bug and how we can adjust our usage of dh_shlibdeps to avoid these > > warnings? The use of dh_makeshlibs as mentioned in the dh_shlibdebps > > causes no change in behavior. >=20 > The interesting thing is that the code generating this warning only > changed from > &warn("format of $1 not recognized"); > to > &warn("format of \`NEEDED $1' not recognized"); >=20 > No other code leading to this warning has changed. The warning should > have been displayed before but it wasn't. I can only guess that to > be a very, very weird perl bug. [...] Suddenly it's all very clear :-). The code in java-package was suppressing the warning being generated by dpkg-shlibdeps via the following quite brittle method: # suppress some warnings dh_shlibdeps -l"$ldpath" 2>&1 |=20 { grep -v "warning: format of lib.*\.so not recognized" >&2 || true; } echo " dh_gencontrol" Since the text of the warning string changed, the warnings are now not being suppressed. Sorry for the confusion. Regards, --=20 Barry Hawkins All Things Computed site: www.alltc.com weblog: www.yepthatsme.com Registered Linux User #368650 --=-Y0Ad2YZDqJLKep21a/dr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD6PRlHuKcDICy0QoRAiDsAKC0oLZfXA+5B5Ys5hDiDw1z2GacPACgxiNg y5xeHw11TX+tSU7nvxMHSxs= =20vt -----END PGP SIGNATURE----- --=-Y0Ad2YZDqJLKep21a/dr--
--- End Message ---
