Bug#919162: lintian.d.o apears to report many failures twice
On Wed, 2019-01-16 at 23:03 +0000, Chris Lamb wrote:
> 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...?
I don't know about the two x86 variants -- I suppose there must be some
variability (maybe rules has an ifeq(...,amd64) which really wanted to
check both), but it would seem more likely there would be more
opportunity for differences on more "distinct" architectures.
>
> … 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
That's what I was thinking for the ideal case too.
Less ideal but an acceptable improvement over today (if for some reason
the above is hard/time consuming to achieve) would be:
> * usr/lib/android-sdk/build-tools/debian/aapt [amd64]
> * usr/lib/android-sdk/build-tools/debian/aapt [i386]
> * usr/lib/android-sdk/build-tools/debian/aapt2
But if more arch's are added that becomes less and less palatable I
think.
Ian.
Reply to: