Thanks for the clarification. I'll add some code to my systems that are running lintian to work around this then.
I guess you can close the bug - thanks for the information. Regards, Andrew McMillan. On Fri, 2026-02-27 at 11:02 +0000, Adam D. Barratt wrote: > On Fri, 2026-02-27 at 14:15 +1300, Andrew McMillan wrote: > > You are correct that I am running on amd64 and looking at a package > > which was built on arm64. > [...] > > My point is that I don't believe anyone is building and uploading > > NEW > > packages on i386 but increasingly people are doing so on arm64, and > > so the search that lintian is doing through the list of > > _arch.changes > > files it prints should really include _arm64.changes (and > > realistically it could probably drop _i386.changes, but that's not > > really necessary). > > As Nilesh alluded to in a previous response, Lintian isn't using a > hard-coded list here that includes i386 and could have arm64 added to > it. > > Rather, it's using the set of architectures that your system knows > about. The only hard-coded entries are "multi", "source", and "all". > Anything else is determined at run-time, specifically: > > - $DEB_BUILD_ARCH, if set > - the result of "dpkg --print-architecture" otherwise > - $DEB_HOST_ARCH, if set > - the result of "dpkg --print-foreign-architectures" > > The relevant section of the code is > https://salsa.debian.org/lintian/lintian/-/blob/master/bin/lintian?ref_type=heads#L880-909 > > Regards, > > Adam -- ---------------------------------------------------------------------- Porirua, New Zealand +64 (27) 288 6741 Bruce Schneier can log into any computer just by staring down the prompt. ----------------------------------------------------------------------
