Your message dated Wed, 25 Mar 2020 11:04:45 +0000 with message-id <e1jh3q1-0009dt...@fasolo.debian.org> and subject line Bug#954798: fixed in lintian 2.60.0 has caused the Debian Bug report #954798, regarding lintian: field-too-long checksums-sha256 error to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
Description: Binary data
Description: Binary data
--- End Message ---
--- Begin Message ---Source: lintian Source-Version: 2.60.0 Done: Chris Lamb <la...@debian.org> We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb <la...@debian.org> (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 25 Mar 2020 10:56:21 +0000 Source: lintian Built-For-Profiles: nocheck Architecture: source Version: 2.60.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers <lintian-ma...@debian.org> Changed-By: Chris Lamb <la...@debian.org> Closes: 954146 954484 954763 954798 954803 954819 Changes: lintian (2.60.0) unstable; urgency=medium . * Summary of tag changes: + Added: - runtime-test-file-uses-installed-python-versions - upstream-metadata-not-yaml-mapping . [ Chris Lamb ] * Do not check the length of Checksums-Sha256 fields. (Closes: #954798) * Don't check for an md5sums control files in udebs. (Closes: #954803) * Expand possible-missing-colon-in-closes to also check for semicolons used in place of colons. (Closes: #954484) * Check for calls to py3versions -i in autopkgtests. (Closes: #954763) . [ Felix Lechner ] * Do not run the fields/length check on .changes or .buildinfo files. (Closes: #954146) * Check for upstream metadata without a YAML mapping at the "document" level. . [ Scott Kitterman ] * Update "old" and "ancient" python-version-field tags descriptions to suggest also checking for incorrect use of "py3versons -r". (Closes: #954819) Checksums-Sha1: d464ad2c2eddc0726fdcc21255f771b6912e3a73 4158 lintian_2.60.0.dsc f435612f2d277df5b4e58e07827d6242254a4bec 1876580 lintian_2.60.0.tar.xz 715c4da25e7dbdbf615a736281dd8ba584695f1c 6095 lintian_2.60.0_amd64.buildinfo Checksums-Sha256: 438712d6fe9bee09cd19376c4f310950218fd0bd382f39e9e535a9cfb0b54dd3 4158 lintian_2.60.0.dsc 703943a1dc31db92d399435fc9cd40d77a538c11db6dcc0004353dfaa7dd81c3 1876580 lintian_2.60.0.tar.xz 1d8562f549936f63285294643c82f473be27632144b0099cc29e0c1a97009b4a 6095 lintian_2.60.0_amd64.buildinfo Files: c3dcd758ed3466e5e695bab4d4f1b813 4158 devel optional lintian_2.60.0.dsc 5d1ef57cfeefc13788876372dba66a3d 1876580 devel optional lintian_2.60.0.tar.xz 996c7890e7e2ffad3ea16f9a24916cac 6095 devel optional lintian_2.60.0_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl57OWgACgkQHpU+J9Qx Hlia4RAAtBFS5yIVaU/JuuDfsNoAe+l5LboYU42/Q5uj0SjlycgLp9e+5kRgkqOx NV6usRsYUfKW8/I53bN0YnOapZKKp5ghKvJSPsMigaQ6uOYz+wcP6fgGJj3i+WtE oo+qmVS+rSC1YF3W4jxfteyxRiwoSQWyN4tRc/kZnoAKrfSljRhBLssMQPv6M8vS suHkhv8evu9mBu6IbBOk9rKBOwOpLR+QctZ01RjIfrXP08WVBcZCWGq3qV5PXYda SwDZrbIaBmWz4xIQdRT7gNLbTDMCVIVIiRpnW4SEFqzx0sjRFqXghW2R7YQDS7hs hWAysAVYvfn60khwdbS6oL6LxUL1WG4ACIQp0Op+xX/2mRt3Gv7t+njqUHkiEJO5 EawlGPI11zgwatb3PNeB44Dp2bdcmS2QfvGeMDZeVIj5b88pi2VusTh2oznew7h6 sZgEw/GXMf6rTh8DnODMY3fNNidCVH7LNEj/vol1/uxmyIEOKX3CBTSO8WSyUHZT kKtb/8thU7iRBBi/mQTsHJefWeVfpkUCZk9x2EioM+WiG3hpNB+3DX2FV4cFUe3u yTaeln/P8oCy1NbzOQuOsCpHfelife881+oNHv1zl6OWPacRyMCziJBwTtapZuuk oKRviKZms9BEl9VwcrgTpUc9gVy/QGA9edLpNJOM8SSX6S5NCxQ= =5/tq -----END PGP SIGNATURE-----
--- End Message ---