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 chars > 5000) E: budgie-extras buildinfo: field-too-long Checksums-Sha256 (5321 chars > 5000) * What exactly did you do (or not do) that was effective (or ineffective)? sbuild using unstable Note - no additional binaries were added in this upload - the new version of lintian threw up these issues * What was the outcome of this action? E: budgie-extras changes: field-too-long Checksums-Sha256 (5432 chars > 5000) E: budgie-extras buildinfo: field-too-long Checksums-Sha256 (5321 chars > 5000) * What outcome did you expect instead? I wasnt expecting this issue. It does seem a little restrictive especially since the sha256 field checksum for each of the binaries is relatively long as you would expect. I suppose I could "split" the package rather artificially - maybe one python based binaries and one vala based binaries with the current budgie-extras package as a "metapackage" - I'm really seeking advice how too proceed - I don't want to upload the fixes with these lintian errors that break policy attached are the changes and buildinfo files
Attachment:
budgie-extras_0.94.0-1_amd64.buildinfo
Description: Binary data
Attachment:
budgie-extras_0.94.0-1_amd64.changes
Description: Binary data