Hi, Marga Manterola <ma...@google.com> (2016-04-07): > On Thu, Apr 7, 2016, 19:18 Niels Thykier <ni...@thykier.net> wrote: > > > What tags are you observing with your dbgsym packages? Ideally the > > debhelper generated packages should be fully policy compliant with no > > lintian warnings (provided you use an up to date lintian). > > > > It was an internal package that shipped binaries that had been > pre-compiled, thus missing debugging symbols (the .debug files did > have the strings though, as the original binaries were unstripped).
I'm seeing the same issue on buster when preparing a customer's package
that relies on an external supplier's shared object that's unstripped
initially but doesn't seem to output anything interesting in the auto
-dbgsym package.
I resorted to manually creating this directory and shipping the
debian/my-package-dbgsym.lintian-overrides through a dh_lintian
override:
debian/.debhelper/my-package/dbgsym-root/usr/share/lintian/overrides/
Looking at https://sources.debian.org/ it seems some other maintainers
have tried stashing such a debian/their-package-dbsym.lintian-overrides
in their source tree… ;)
Cheers,
--
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
