Hi!

Was recently introducing an automatic debug symbol package, and got
this lintian warning, which seems just wrong. I think the correct way
to go about emitting it would be to:

  - Check for the m/--(?:ddeb|dbgsym)-migration=/ and extract the
    version in the argument list (if possible, probably emit if the
    version cannot be extracted?).
  - Lookup the closest version in the debian/changelog, and fetch the
    date for that entry.
  - Lookup the $name for the current $distro release.
  - Lookup the initial date for the previous ($name-1) $distro release.
  - Check whether the changelog entry date is earlier than $name-1 date,
    and only if so, emit the tag.

Thanks,
Guillem

tags 940748 + moreinfo
thanks

Hi Guillem,

[..]

Thanks for the implementation idea. However, could you give the
concrete details why you were seeing a false-positive here, especially
why it was not "possibly complete" and how/wy the date of the
distribution's release is relevant?


Regards,

Whether a migration has been complete and can be removed is determined
exclusively by when the migration code got introduced, so it can only
be removed when it has already been part of a stable release. From the
tag's own description:

  ,--- [ lintian-info --tags debug-symbol-migration-possibly-complete ]
  […]
  N:   If this command was added to the debian/rules that was included in the
  N:   current stable release of Debian then it can possibly be removed.
  N:
  N:   However, if the command was added later (and/or the package was not
  N:   included in stretch) please wait until it has been included in a
  N:   stable release before removing it.
  […]
  `---

So, adding the migration code now to a package in unstable will emit
this tag, even if it should not be acted on until the package has been
part of the next release. Adding an override until then would defeat
the purpose of the tag, as then yuo'd need to recall checking them all
after the release. :)

Thanks,
Guillem