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.
Hi
On Tue, Mar 24, 2020 at 8:39 AM Chris Lamb wrote:
>
> > now Chris whitelisted this field from the check. But really the whole
> > file should be.
I have no issue disabling the check for buildinfo files. I just
thought that examining them was a stated goal, and your suggestions do
not work in
Mattia,
> On Mon, Mar 23, 2020 at 04:06:20PM +, 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 c
On Mon, Mar 23, 2020 at 04:06:20PM +, 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 whol
Package: lintian
Version: 2.59.0
Severity: normal
Dear Maintainer,
* What led up to the situation?
sbuild -d unstable for the latest version of my package budgie-extras
threw a policy errors for this particular field
E: budgie-extras changes: field-too-long Checksums-Sha256 (5432 ch
5 matches
Mail list logo
