Bug#954798: lintian: field-too-long checksums-sha256 error
Mattia,
> On Mon, Mar 23, 2020 at 04:06:20PM +0000, David Mohammed wrote:
> > E: budgie-extras changes: field-too-long Checksums-Sha256 (5432 chars > 5000)
> > E: budgie-extras buildinfo: field-too-long Checksums-Sha256 (5321 chars > 5000)
>
> now Chris whitelisted this field from the check. But really the whole
> file should be.
I agree but I suspected there is some reason why we don't revert the
"sub binary" conditional (changed in 14fa5a80b) in this file, hence
simply adding to pre-existing field whitelist.
> If you are going to whitelist stuff, this would also mean [..] and
> whatever things might appear in the future.
Yeah, this just gets silly. :) Felix, is there something we are
missing regarding why don't return to "sub binary" instead of "sub
always" here?
(Regarding whether the check should even be here, I'm stepping out of
that one I'm afraid but for reference it was added in #942493.)
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org 🍥 chris-lamb.co.uk
`-
Reply to: