On 20/03/2020 13:21, Matthias Klose wrote:
> On 3/20/20 2:15 PM, Felix Lechner wrote:
>> Hi Matthias,
>>
>> On Fri, Mar 20, 2020 at 5:57 AM Matthias Klose wrote:
>>> so please differentiate between Fortran and Modula-2 modules.
>> I have had some issues differentiating gfortran modules (#948033)
Hi,
> gzip: stdout: Broken pipe
This commit reduces the program error to a misidentification:
https://salsa.debian.org/lintian/lintian/-/commit/5b0bff88afd220ecee71897fa0cb2227f14d10dc
The search should also be restricted to expected locations for
gfortran modules. Please do not close the
On 3/20/20 2:15 PM, Felix Lechner wrote:
> Hi Matthias,
>
> On Fri, Mar 20, 2020 at 5:57 AM Matthias Klose wrote:
>>
>> so please differentiate between Fortran and Modula-2 modules.
>
> I have had some issues differentiating gfortran modules (#948033). In
> which folders do they usually reside,
Hi Matthias,
On Fri, Mar 20, 2020 at 5:57 AM Matthias Klose wrote:
>
> so please differentiate between Fortran and Modula-2 modules.
I have had some issues differentiating gfortran modules (#948033). In
which folders do they usually reside, please?
Also, why are they not all named md.gz, as in
Package: lintian
running lintian on a gcc-10 build, I see
gzip: stdout: Broken pipe
gzip:
/tmp/temp-lintian-lab-i1Mvu3Lp4j/pool/g/gcc-10/libgm2-10-dev_10-20200320-1_amd64_binary/unpacked/usr/lib/gcc/x86_64-linux-gnu/10/m2/m2cor/Debug.mod:
not in gzip format
and then continues with:
libgm2-10-
5 matches
Mail list logo