From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question regarding rootfile warning "Error! '/aarch64' in
 rootfiles files found!"
Date: Thu, 09 Dec 2021 19:41:18 +0000
Message-ID: <FFEF8F76-8414-41FB-BE71-4CE13CFBF158@ipfire.org>
In-Reply-To: <98b261ef-86dc-f60c-0dfc-8350749d563a@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5368396214067188259=="
List-Id: <development.lists.ipfire.org>

--===============5368396214067188259==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,

What is the bug for? The check does exactly what it is supposed to do.

We either need to get rid of it entirely because it has false positives or we=
 need to have a whitelist.

Is that a solution that you had in mind?

-Michael

> On 9 Dec 2021, at 19:39, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wro=
te:
>=20
> P.S.: Bug #12743 (https://bugzilla.ipfire.org/show_bug.cgi?id=3D12743) has =
been raised for this.
>=20
> Should anybody have spare time to work on it, please feel free to do so. :-)
>=20
>> Hello Adolf,
>>=20
>> thanks for your reply.
>>=20
>>> How should we deal with the situation where a source file filename happen=
s to use an architecture name the same as an IPFire name.
>>=20
>> I also think this is a false positive, though it surprises me we never cam=
e across this
>> scenario all the years before. Either way, make.sh (or whatever's doing th=
is check) needs
>> to be updated to ignore such cases.
>>=20
>> I'll file a bug for this later...
>>=20
>> Thanks, and best regards,
>> Peter M=C3=BCller
>>=20


--===============5368396214067188259==--