Hi Ian & Niels, > I: grub-common binary (2.02+dfsg1-10) [amd64]: hardening-no-bindnow usr/ > bin/grub-editenv > I: grub-common binary (2.02+dfsg1-10) [i386]: hardening-no-bindnow usr/ > bin/grub-editenv
TIL we check both x86 architectures. Why do we do this out of interest? Are there examples of tags we would only find on one but not the other...? If we retain it I guess we need to make this more concise or at least clearer; it certainly looks like a bug right now. So, to use the following as concrete example, here's what we currently display: aapt 1:8.1.0+r23-3 (binary) ($maintainer) * usr/lib/android-sdk/build-tools/debian/aapt * usr/lib/android-sdk/build-tools/debian/aapt2 * usr/lib/android-sdk/build-tools/debian/aapt … what would be the ideal output? Perhaps: aapt 1:8.1.0+r23-3 (binary) ($maintainer) * usr/lib/android-sdk/build-tools/debian/aapt [amd64, i386] * usr/lib/android-sdk/build-tools/debian/aapt2 Thoughts? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-