Hi
On Tue, 01 Nov 2022 18:43:31 -0400 Daniel Kahn Gillmor wrote:
> This error is also mistakenly produced for libassuan-mingw-w64-dev (used
> for cross-building gpgv.exe as part of a windows installer signature
> verification tool):
Lintian also potentially produces the no-code-sections report
On Fri 2022-02-11 12:51:06 -0800, Felix Lechner wrote:
> I confirmed that Lintian's invocation produces that error for
> usr/lib/dxvk/wine64-development/d3d10.dll.a in dxvk, but how can we
> tell such archives apart from those that are legitimately broken?
This error is also mistakenly produced
On Fri, 11 Feb 2022 12:51:06 -0800 Felix Lechner
wrote:
> On Fri, Feb 11, 2022 at 12:09 PM Marc Dequènes wrote:
> >
> > Could you consider improving the check?
>
> Yes, I'd like to.
>
> > readelf fails with "readelf: Error: Not an ELF file - it has the wrong
> > magic bytes at the start"
>
>
Hi,
On Fri, Feb 11, 2022 at 12:09 PM Marc Dequènes wrote:
>
> Could you consider improving the check?
Yes, I'd like to.
> readelf fails with "readelf: Error: Not an ELF file - it has the wrong
> magic bytes at the start"
I confirmed that Lintian's invocation produces that error for
Package: lintian
Version: 2.114.0
Quack,
no-code-sections is triggered on dxvk, and also on wine, but these are
not ELF files since it's targeted for Windows. Of course an override is
possible but here there's an obvious way to avoid a false positive since
readelf fails with "readelf:
5 matches
Mail list logo
