Bug#954341: lintian: What's going on with "field-too-long Installed-Build-Depends"?

[Felix Lechner <felix.lechner@lease-up.com>]

Hi,

On Fri, Mar 20, 2020 at 8:03 AM Mattia Rizzolo <mattia@mapreri.org> wrote:
>
> field-too-long was added to prevent silliness in the archive.  As such, it only makes sense for binary control fields and .dsc, nothing else.

Why should fields in buildinfo and changes files be treated
differently from fields elsewhere?

> ie. "sub binary" → "sub always" ?

I could have used 'sub installable' to examine only deb and udeb, but
I think it makes sense to examine fields everywhere. Fields that are
allowed to be long can be exempt.

The broader issue of duplicate tags across group components, which is
related to the true issue here, will be addressed when tags are
filtered and prioritized for printing. At that point, tags that point
to the origin of something will suppress tags that merely received a
value by copying.

> E: pkg-perl-tools buildinfo: field-too-long Installed-Build-Depends (11190 chars > 5000)

I will disable the tag for this particular buildinfo field in the near future.

Kind regards

Felix Lechner