Hi, On Fri, May 04, 2018 at 08:47:13PM +0200, Graham Inggs wrote: > On 4 May 2018 at 01:16, Chris Lamb <la...@debian.org> wrote: > > Could you have an initial stab at the description for this tag and, > > perhaps, a suggested severity level? :-) > > I: auto-dbgsym-migration-possibly-complete > > debian/rules contains 'dh_strip --dbgsym-migration' (formerly > '--ddeb-migration') > > Automatic debug symbol packages first became available in December 2015. > > If the dh_strip command migrating manual '-dbg' packages to '-dbgsym' > was added to debian/rules and the package was included in Stretch, > then the command, and possibly 'override_dh_strip', may now be > removed. If the command was only added later, and/or the package was > not included in Stretch, please wait until it has been included in a > stable release before removing it. > > Further information: > https://wiki.debian.org/AutomaticDebugPackages
I advise against such tag.
Whilst true that several packages could potentially remove the
"migration" path, and IMHO even for most of the ones that added it it
wouldn't have been necessary, packages that today migrate from a manual
dbg to an automatic dbgsym and have any likelyhood of file clashing due
to the built binaries having the same build-id would have to use that
flag. Doing something recommended (moving to dbgsym) and have that
trigger a lintian tag —even if it is not a warning— would be very
annoying.
Graham: what is your reasoning for pushing toward what feels like a
deprecation of --dbgsym-migration? I've never heard any deprecation
plan from Niels, and surely a versioned Breaks+Replaces in dbgsyms are
not causing any issues.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
