Your message dated Fri, 17 Jan 2020 21:52:00 +0000 with message-id <[email protected]> and subject line Re: debhelper: dh_shlibdeps does not always call dpkg-shlibdeps has caused the Debian Bug report #862909, regarding debhelper: dh_shlibdeps does not always call dpkg-shlibdeps 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.) -- 862909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862909 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: debhelper Version: 10.2.5 Severity: normal Hi! When a package does not contain any candidates that dh_shlibdeps considers worth passing to dpkg-shlibdeps, it does not call dpkg-shlibdeps, even if dh_shlibdeps got called with additional arguments, which in most cases will contain a list of files to analyze. This is because $dh{U_PARAMS} or a subset of that is not part of @filelist. Say a package with only plugins that dh_shlibdeps does not recognize, and then doing this manually: dh_shlibdeps -- path/to/plugins/foo.plugin In my particular case the files involved were nodejs bindings, which are recognized in later debhelper versions, but the principle applies to any other unsupported files. This was very surprising and took some debugging to track down, because it seemed very non-obvious behavior. :) Thanks, Guillem
--- End Message ---
--- Begin Message ---Source: debhelper Source-Version: 11 On Thu, 18 May 2017 16:25:34 +0200 Guillem Jover <[email protected]> wrote: > Package: debhelper > Version: 10.2.5 > Severity: normal > > Hi! > > When a package does not contain any candidates that dh_shlibdeps > considers worth passing to dpkg-shlibdeps, it does not call > dpkg-shlibdeps, even if dh_shlibdeps got called with additional > arguments, which in most cases will contain a list of files to > analyze. This is because $dh{U_PARAMS} or a subset of that is not > part of @filelist. > > Say a package with only plugins that dh_shlibdeps does not recognize, > and then doing this manually: > > dh_shlibdeps -- path/to/plugins/foo.plugin > > In my particular case the files involved were nodejs bindings, which > are recognized in later debhelper versions, but the principle applies > to any other unsupported files. > > This was very surprising and took some debugging to track down, > because it seemed very non-obvious behavior. :) > > Thanks, > Guillem > > Hi, I believe this is resolved in compat 11, where dh_shlibdeps will find all ELF files instead of only checking a small whitelist of possible ELF files. While the concrete behaviour you observed remains, the use case for passing an ELF directly should no longer be necessary. Relatedly, this also means that dh_shlibdeps can avoid having to understand parameters passed to dpkg-shlibdeps (which is the preferred choice for dh_* tools). Thanks, ~Niels
--- End Message ---
