On Tue, Mar 24, 2020 at 09:04:52AM -0700, Felix Lechner wrote:
> I will disable this check for buildinfo files later today.
(and .changes please :))
> On a larger scale, the high number of complaints we received about
> this check from the broader community (and from our own team members,
> i.e. mattia) raise the question whether Lintian should be concerned
> about output generated by dpkg and friends.
It probably should, as IMHO dpkg should stay as dumb as possible and
trust what the maintainer asks it to do.
Also, not everything dpkg can do is acceptable for the Debian archive,
but there are also other targets out there.
> I agree with all of you (and have stated numerous times in the record)
> that Lintian provides friendly packaging advice for the benefit of
> maintainers. We are not dpkg's test suite. For that reason, I am happy
> to remove this check from Lintian as long as an equivalent restriction
> finds its way into dpkg.
Such check will never appear in dpkg, that's totally out of its scope.
dpkg and apt work just fine with incredibly huge amount of data, this
restriction is really artificial.
The fact that a field is overblown can only work as a red herring in
some cases, like the past Provides field that was way too long and
turned out to be mostly unnecessary.
--
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