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.
If you are going to whitelist stuff, this would also mean:
Description
Changes
Files
Checksums-Sha1
Checksums-Md5
Environment
and whatever things might appear in the future. Really nothing cares
about the lenght of .changes and .buildinfo fields, and those fields are
thought that way to be however long they need to be.
I'll admit that IMHO the whole check is silly (saying that a random
field can't be over 5k char, very arbitraly?). There was *one* thing
that broke (reprepro) that was fixed already… I totally don't
understand what this tag is trying to accomplish.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature