Hi Nilesh, You are correct that I am running on amd64 and looking at a package which was built on arm64.
I am reviewing packages in the NEW queue and one of my review steps is to run lintian on them. All of these packages have a .changes supplied along with the upload, but in some cases it is arm64, and so lintian cannot find it. If I manually specify the .changes file everything works as expected. 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). It's an inconvenience to me, and I can work around it by running: lintian -options ../$(basename $PWD)_*.changes Thanks, Andrew McMillan Member of the DFSG Licensing and New Packages Team On Thu, 2026-02-26 at 21:23 +0530, Nilesh Patra wrote: > On 26/02/26 2:16 pm, Andrew McMillan wrote: > > Package: lintian > > Version: 2.129.0 > > Severity: normal > > > > This failed for me: > > > > $ lintian -Iiv --show-overrides --color=always > > > > Cannot find a changes file for sc-membench/1.2.1-1. It would be > > named > > like: > > sc-membench_1.2.1-1_amd64.changes > > sc-membench_1.2.1-1_i386.changes > > sc-membench_1.2.1-1_multi.changes > > sc-membench_1.2.1-1_all.changes > > sc-membench_1.2.1-1_source.changes > > in any of those places: > > .. > > ../build-area > > /var/cache/pbuilder/result > > > > I tried this on amdahl and it seems to work. Something seems to be > off in > your local environment. > > > nilesh@amdahl ~/hello/hello-2.10 > > % ls ../ > > hello-2.10 hello_2.10-5.debian.tar.xz > > hello_2.10-5_arm64.buildinfo hello_2.10-5_arm64.deb > > hello_2.10.orig.tar.gz.asc > > hello-dbgsym_2.10-5_arm64.deb hello_2.10-5.dsc > > hello_2.10-5_arm64.changes hello_2.10.orig.tar.gz > > and then- > > > nilesh@amdahl ~/hello/hello-2.10 > > % lintian -Iiv --show-overrides --color=always > > N: > > I: hello: hardening-no-bindnow [usr/bin/hello] > > N: > > N: This package provides an ELF binary that lacks the "bindnow" > > linker flag. > > N: > > N: This is needed (together with "relro") to make the "Global > > Offset Table" (GOT) fully read-only. The bindnow feature trades > > startup time for improved > > N: security. Please consider enabling this feature or consider > > overriding the tag (possibly with a comment about why). > > N: > > N: If you use dpkg-buildflags, you may have to add > > hardening=+bindnow or hardening=+all to DEB_BUILD_MAINT_OPTIONS. > ... > > Are you sure you have the .changes file? > What is the output of `dpkg --print-architecture` and `dpkg --print- > foreign-architectures`? > Are you trying to run lintian for an arm64 package on amd64 machine? > (Your output suggests that the machine is amd64) > > Best, > Nilesh -- ---------------------------------------------------------------------- Porirua, New Zealand +64 (27) 288 6741 I have not seen high-discipline processes succeed in commercial settings. - Alistair Cockburn ----------------------------------------------------------------------
