Bug#948033: lintian: Fortran test fails on 'flang' mod files

[Felix Lechner <felix.lechner@lease-up.com>]

Hi Alastair,

On Fri, Jan 3, 2020 at 6:33 AM Alastair McKinstry <mckinstry@debian.org> wrote:
>
> /usr/share/lintian/checks/fortran.pm checks the 'mod' files for Fortran.

To make space for flang, the gfortran check was moved to
checks/fortran/gfortran.pm.

> I'm adding support for the flang fortran compiler , which ships mod files that are in a different format.
>
> flang mod files should be found in $LIBDIR/fortran/flang-$(version)

The gfortran check now disregards paths containing /flang-\d+/.

Gfortran modules do not appear to be similarly contained. For example,
libopenmpi-dev ships both

    /usr/lib/x86_64-linux-gnu/openmpi/lib/mpi.mod
    /usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/mpi.mod

They look identical but are not linked (and carry different
permissions). Also, gfortran itself ships modules in yet another
location, such as

    /usr/lib/gcc/x86_64-linux-gnu/8/finclude/openacc.mod

The file magic for these modules is merely 'gzip', which means we have
to use paths to distinguish them. If you have any say, it might make
sense to group gfortran modules in fewer places.

Grub and Libreoffice also ship .mod files. They are likewise excluded.

> New lintian tests should be added

We are happy to create a new check in checks/fortran/flang.pm for you
when you are ready.

Kind regards
Felix Lechner