Bug#954415: hundreds of wrong binary-is-wrong-architecture warnings

[Jiri Palecek <jpalecek@web.de>]

On Wed, 25 Mar 2020 07:11:02 -0700 Felix Lechner wrote:

> Hi,

Hello,

>
> On Sat, Mar 21, 2020 at 4:51 AM Matthias Klose wrote:
> >
> > I don't know when that was introduced, but you see some hundred of those in the
> > gcc-N packages:
>
> The tag was introduced when the sole Lintian check provided by the
> xdeb package became part of Lintian. Given recent changes, it was too
> cumbersome to keep filing bug reports [1] and merge requests [2] for
> dependent packages. The relevant commit was:
>
> https://salsa.debian.org/lintian/lintian/-/commit/25013ff8173883796e00f4bc58a89f2a09839727

>

This is the problem:

$self->tag('binary-is-wrong-architecture', $file)

if ( $architecture =~ /^arm[el|hf]$/

&& $file->file_info !~ /ARM,(?: EABI5)? version 1 \(SYSV\)/)

|| ( $architecture eq 'i386'

&& $file->file_info !~ /x86-64, version 1 \(SYSV\)/)

If architecture is i386 (OK, mine is), but file info DOESN'T indicate x86-64 (yes, 386 binaries don't), we tag the package. That can't be right; I don't want x86-64 files on a 386 system. And I want 386 binaries instead. Please fix that.

As an aside, why is that test even necessary? The next line (... !~ $pattern) should work fine for i386.

Regards

    Jiri Palecek