Hi Vincent,
On Thu, Dec 5, 2019 at 2:32 PM McIntyre, Vincent (CASS, Marsfield)
<vincent.mcint...@csiro.au> wrote:
>
> I can't see anything in policy that requires these naming minutiae.
We would like to shed the image of enforcer. Only a few Lintian tags
relate to policy. Lintian provides packaging advice for the benefit of
maintainers.
> + } elsif ($basename =~
> m/^(?:.*\.)?(?:changelog|NEWS|TODO).[dD]ebian$/o) {
My check does not currently implement the lowercase 'd'. Please let me
know if you would like to have it.
> Do you think there should be some restriction to avoid this warning
> when something other than debhelper is in use?
On something like this, which is both useful and rare, I will wait for
bug reports to complain.
> I'm not sure what that something other would be.
There are other build systems. You can find a relative measure of
their popularity on https://trends.debian.net/#build-systems.
> - debian/README is ignored
I am reluctant to do anything about it. Is the file sometimes used for
unpublished developer notes?
> - debian/TODO gets shipped as /usr/share/doc/rkhunter/TODO.Debian,
> ie not gzipped.
> - debian/TODO.Debian is ignored.
Thanks for looking into it. I also added TODO:
https://salsa.debian.org/lintian/lintian/commit/54e2611c0a65d5377ddb0abb055b8105019e974b
> This was debhelper 12.1.1~bpo9+1, if that matters.
You may wish to amend #429510 with information about the new Lintian
tags if they work for you. You could even mention the unison bug and
gently remind the debhelper folks that the issue remains open.
Kind regards,
Felix Lechner
