Hi,

as suggested by Chris Lamb I hereby asking for either ignoring or
setting severity to either experimental or pedantic for certain teams
for the issue

    script-with-language-extension

This should happen for the teams

   Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
   Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>

Kind regards and thanks for maintaining lintian

     Andreas.


[1] https://lists.debian.org/debian-med/2020/04/msg00248.html

Hi,

Lintian gained a facility recently [1] that makes granting such
extensions a breeze. The goal is to accommodate toolchains or upstream
package sets that are out of Debian's control, and hence hard to fix.
Unfortunately your desired method of selelction—by Debian team—does
not qualify as a meaningful indicator for being outside your control.
Do you have another way to identify the class of packages affected?

For an example related to Emacs, please see here. [2]

Also, please allow me to point out the JSON facilities on Lintian's
new website. [3] Several other teams love it. Thank you!

Kind regards
Felix Lechner

[1] https://salsa.debian.org/lintian/lintian/-/commit/8c3d587559cfbdf5dd41e9ba1f66c9ab52de577e
[2] https://salsa.debian.org/lintian/lintian/-/commit/24c509ee83ab2a1530a52ab3875c57ab99ad2085
[3] https://lintian.debian.org/query

Hi Felix,

Nice.

The best I can say is this kind of "summary" of our discussion about
this topic[4].  We simply do not control the scripts of scientists who
expect those names they find in publications.

So it is actually a decision that is drawn by a team not to rename
anything that will be expected in the original name by the users for
known reasons.  Since it belongs to the policy of the teams it is IMHO
the most straightforward way to deal with the issue to parse the team
name.

Kind regards and thanks for working on lintian in any case

    Andreas.

[4] https://lists.debian.org/debian-med/2018/06/msg00043.html